api-playground VS obsidian-wielder

GitLab team member here.

Maybe you can re-use the script I shared in this comment [0] to query the GitLab REST API to generate an index. I'm a fan of using the API programmatically, and tend to avoid git checkout/grep/etc. inside CI/CD pipelines (works too, everyone is free to choose their way).

Yet again, I love API challenges, so I've created a new script which parses a defined markdown footer for Tags and Due date, and generates an ordered index by due date. I did not know which format you are using, so I made up my own, see the MR description [1] and docs [2].

The script lives in [3] and is a mix of fetching files, parsing content with regex, and generating the index + creating a commit to upload automatically.

A demo overview is shown in [4] with the generated index.md, ordered by due date and linking the files by parsed heading title, file paths, and tags.

Hope it helps, feel free to repurpose, or ping me for questions on the GitLab community forum [5]. My Python code is a little rusty, I am slowly adopting all the 3.x design patterns after many years with 2.x.

I might follow your idea with notes and custom footer parsing. That's a really nifty idea, and helps solve my own chaos :-)

[0] https://news.ycombinator.com/item?id=32155848

[1] https://gitlab.com/dnsmichi/api-playground/-/merge_requests/...

[2] https://gitlab.com/dnsmichi/api-playground/-/tree/main/pytho...

[3] https://gitlab.com/dnsmichi/api-playground/-/tree/main/pytho...

[4] https://gitlab.com/dnsmichi/api-playground/-/tree/main/demo/...

[5] https://forum.gitlab.com/u/dnsmichi/summary

Depending on which particular subject you are interested in:

- The plugin:

https://wielder.victor.earth/Welcome shows the sort of things you can build with Wielder. The github repository for the library is here https://github.com/victorb/obsidian-wielder

- How To Solve it

The key ideas behind How To Solve It are that for a lot of our challenges there are strategies we can use to tackle them effectively. How To Solve It expounds on how to go about understanding a problem, understanding the connection of the data you have with what you don't know, how to make problems more tractable, carrying out a plan, and evaluating the results.

- Untools

A site dedicated to listing various strategies for thinking, communicating and prioritization; they sell templates similar in nature to what I'm building, but I depart sharply from them in my desired document representation choice for templates - Zettlekastian graph continuations for me versus linear documents for them.

- My own tool

This is currently private and not yet ready for public consumption. I have a whole lot of philosophical backing for what I'm trying to build but it is still very far from generating utility at the level I want it too. Later today I'll see about moving some private notes into a blog post going into more depth about what I'm building and why.