Please add support for the category folders as documented by jekyll

[sparksis]

While Siteleaf does a commendable job of safely flattening the site it triggers an organizational breakdown of content in the repo.

Unlike tags, categories for posts can also be defined by a post’s file path. Any directory above _posts will be read-in as a category. For example, if a post is at path movies/horror/_posts/2019-05-21-bride-of-chucky.markdown, then movies and horror are automatically registered as categories for that post. [1]

This structure is critical for keeping thoughts well organized.

Please note that this is a request to retain the directory structure. I think that is still likely a prudent design decision to update the front matter with the computed categories.

---

Please note that it appears that the present behavior used to be in your documentation: siteleaf/learn.siteleaf.com#73 (comment) but does not appear to be present at this time. Ideally if you cannot/will not implement this feature, you re-add this to the documentation for clarity

[sparksis]

The more I think about this, the more I'm confused how this could be a bug. The Siteleaf UI permits modifying Categories inside of a Collection page. This doesn't make sense as collections cannot have category attributes and therefore cannot be programmatically accessed from the api.

It seems like the product team may have inadvertently thought that Collections are intended to be collections of Posts and Pages but based on the documentation they're more akin to structured data (via frontmatter) and static files.

---

A more practical example of how collections use categories:

1. Page created in the UI: image
2. Home page unable to find the named category: image
3. repo: https://github.com/sparksis/siteleaf-feature-request

---

It should however be noted that Jekyll does use the categories for deciding the URL of the pages inside the collection

[sparksis]

The most ideal implementation would probably be to have your content Navigation be a tree view of every folder in the repo that either contains a supported file type (markdown or html). Setting layout: post on any document created in the tree should create the document in a _posts folder such that jekyll is able to more effectively leverage the rich plugin echo system without limitations set by the CMS.