Argentina Ortega
Argentina Ortega
If we add `%% Hub ....%% ` dividers for each individual file, it should be possible to update anything contained between those comments. Updating the templates with these dividers is...
> I presume it's very doable to create a PR for each newly-added plugin note. I think the idea was to open an issue mentioning the plugin dev so they...
I'm still unsure if we should be keeping CSS files under the hub. It feels like these would belong in a different repo. Perhaps we can bring those markdown files...
From our pairing session on saturday: - On websites, ignore any that begin with github.com (duplicated info already in the template) or obsidian.md (failed to update manifest.json) - add a...
Zoottelkeeper and Dangling links are two that we currently use. I've also thought about the best way to distribute these, since the current approach `.obsidian/app.json` causes a lot of issues...
Thanks! I've assigned the issue to you in the meantime
I can't dig out the comment from Discord, but the rough idea was to have a `hub.yaml` file at the root of plugin or theme repos. This would overwrite any...
From our pairing session on Saturday: - Most of the issues on #348 stem from scripted changes, adding the hub.yaml we could interpret these as a trusted source of information,...
Based on the points above, I've made some changes to the original proposal: ```yaml docs: # Link to the plugin documentation hub_content: [], # List of markdown documents to be...