The categories feature was implemented mainly to avoid having to manually add, say, a "news" metadata property to the index.md of every news article. Instead, the system would recognize news articles like we do: based on where they're placed in the filesystem.
But I realized we don't need this additional abstraction. We already have something that'd serve this function: tags. Instead of defining "categories" in the config.json, we could define "autoTagDirs" (or something): directories whose contents will automatically be tagged. Then we can just filter by tag in dynamic pages.
The categories feature was implemented mainly to avoid having to manually add, say, a "news" metadata property to the index.md of every news article. Instead, the system would recognize news articles like we do: based on where they're placed in the filesystem.
But I realized we don't need this additional abstraction. We already have something that'd serve this function: tags. Instead of defining "categories" in the config.json, we could define "autoTagDirs" (or something): directories whose contents will automatically be tagged. Then we can just filter by tag in dynamic pages.