Obsidian-Kirby-Sync next steps

I've been writing for quite some time now, not only on my own blog, but also on the konzentrik blog, for the "Server Side Stories" podcast, and recently also for the Sociabli blog.

Konzentrik and Server Side Stories run under the same domain and use Kirby as CMS and my podcaster plugin. I'm primarily responsible for managing the content there, so it makes sense to extend the Obsidian Kirby Sync setup to it.

I'm currently still scribbling away with pen and paper on how to approach this. Since my article, the Obsidian plugin has changed in a few places. Querying articles in Kirby has become easy: Instead of filling out various fields, an article URL is sufficient. This not only makes working easier, but also paves the way for making the plugin publicly available.

My next step, however, is to expand the settings. The goal is to allow individual folders to be assigned to different API endpoints, on which the Kirby plugin will then listen to. In my case, that would be my own site and konzentrik's.

Depending on which Obsidian folder I execute a sync command in, the corresponding API endpoint is called. The rest should then proceed as usual. It works the same way when uploading articles to Kirby.

Another task I have ahead of me is uploading images. I have no idea how to go about this yet. The images linked in Obsidian are located in a subfolder and need to be uploaded to Kirby in one direction, but also downloaded again when querying articles. I don't have any ideas for this yet.

The next step, however, will be the various API endpoints. I think this can be implemented with manageable effort.