Enhancement: hierarchical workflow for organizing and accessing content within a system.

[yunesco]

The proposed enhancement involves creating a structured and organized system for managing content. Imagine it as a way to organize information similar to how you navigate through folders on your computer.

Creation of Main Categories which is basically the top level folder where the mdx files live:

Start by creating a main category, which we'll call a "Topic Hub." This serves as a top-level container for related content.
Subtopics for Specific Themes:

Within each Topic Hub, you can create subtopics, referred to as "Subject Guides." These Subject Guides represent specific themes or topics related to the main category.
Further Organization with Sub-subtopics:

Optionally, for more detailed organization, you can have sub-subtopics called "Sections." These Sections could contain more specific or detailed information related to the Subject Guides.
User-Friendly Navigation:

When users access the system, they can click on a main category (Topic Hub) to see different themes (Subject Guides) within it. If there are additional subtopics (Sections), they can navigate further to explore more detailed content.
Intuitive Content Exploration:

This structured approach aims to make content organization and exploration straightforward. Users can relate to the concept of navigating through main categories, themes, and subthemes, creating an intuitive and user-friendly experience.

[estruyf]

Thank you, @yunesco, for your suggestion. Could you visualize it in a mockup (it can be very basic)? I just want to make sure that I understand the flow correctly.

[yunesco]

@estruyf Here's a simplified textual representation of how this hierarchical structure might render in a basic UI:

`- Main Categories

• Topic Hub 1
  • index.md
  • Subject Guide 1
    • index.md
    • Section 1
      • content1.md
      • content2.md
    • Section 2
      • content3.md
      • content4.md
  • Subject Guide 2
    • index.md
    • Section 1
      • content5.md
      • content6.md
    • Section 2
      • content7.md
      • content8.md
• Topic Hub 2
  • index.md
  • Subject Guide 1
    • index.md
    • Section 1
      • content9.md
      • content10.md
    • Section 2
      • content11.md
      • content12.md
  • Subject Guide 2
    • index.md
    • Section 1
      • content13.md
      • content14.md
    • Section 2
      • content15.md
      • content16.md
        `

In the UI, these could be clickable elements representing folders. The user would click on the Main Categories to see Topic Hubs, click on Topic Hubs to see Subject Guides, and so on. This provides an organized and intuitive structure for users to explore the content rather than have all content.md files be shown together.

Essentially, the idea is to mimic the folder structure of the content folder and display folders as well for those who prefer a more organized way to access their md files

[yunesco]

And another feature that would be nice if this is implemented is say we navigate to Subject Guide 2, from within that folder, if we click "Create Article" then the article will be generated within that folder without having to navigate manually to that folder

[estruyf]

And another feature that would be nice if this is implemented is say we navigate to Subject Guide 2, from within that folder, if we click "Create Article" then the article will be generated within that folder without having to navigate manually to that folder

This is something FM already supports, more information about this can be found here: https://frontmatter.codes/docs/content-creation/content-types#creating-sub-content

When you would use isSubContent, during the content creation, you'll be able to select the parent folder.