Feedback: move taxonomy.tags/categories/et alii to the .frontmatter subdirectories or the db

[davidsneighbour]

"frontMatter.taxonomy.tags": ["lots", "of", "tags"],
"frontMatter.taxonomy.categories": ["some", "categories"]

I realized these two config items are dynamically updated on content changes. Others for frontmatter values I am not using probably too. If the use of this is to fill dropdowns and keep an index of content, wouldn't it be a better place for them to be either in their own files under .frontmatter/config/taxonomy or even within .frontmatter/content/taxonomyDb.json and categoryDb.json? Updating the config file on content changes feels counterintuitive for the concept of a CMS. Especially non-hierarchical taxonomies might get updated every single time new content is added.

[estruyf]

Are you reading my mind @davidsneighbour 😄. I was thinking about that last week, but I hadn't come up with a solution yet, but you just did.

I love the taxonomyDb.json idea. It makes sense now that I just moved the mediaDb.json to a database folder.

[estruyf]

The tags and categories are now moved to their own taxonomyDb.json file. When you open a project, it will check if tags or categories are present in the DB. If not, it will update it with the one from your settings.