Ideally, I’d like all of Joplin’s configs to travel with Joplin’s other data, including things like user styles and templates. They could live in a special ‘config’ notebook (optionally hidden in the Settings, for instance) and sync like any other notes.
But as long as there is no such thing available, would anyone else be interested in a community-defined guildeline as to where to store third-party configs?
For example, when writing the Ghoplin tool, I’d decided I’d simply create a note with a specific ID (00000000000031337000000000000001, so dibs on that one ) so the tool can always easily find it (and the user can move it to any notebook or rename it in any way, without breaking anything.)
If there were multiple tools/scripts/apps/whatever that wanted to store some config data in Joplin, what do you think would be the best scheme? Everyone just picks a hard-coded note ID and uses it? Some specifically-named config folder every app could place notes into? Something else entirely?
It’s also possible I’m just over-thinking this: if most apps are just bash scripts which only ever run on a single computer, or web-hosted apps like @foxmask’s Jong with their own database, maybe it doesn’t matter at all.