Feature request: Allow for multiple root level ‘component’ folders

[paulrobertlloyd]

Within my components folder, I have a set of components which are top-level (page) assemblies. Conceptually, these are still components, but in terms of my deliverable, they are markedly different. Currently I have made the distinction in the navigation by using italics:

Ideally, the Web UI would allow me to place them under a top level heading instead, i.e.:

This might be a Mandelbrot issue (and one that could be solved by using a custom theme), but it’s worth pointing out that allowing only a single component folder is a notable opinion within Fractal.

[sbaechler]

What about even giving up the strict separation between Handlebars 'Components' and Markdown 'Documentation'? Ideally Fractal would render whatever you throw at it.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mihkeleidast]

Solution proposal

• Allow specifying root: true in a collection config.
• By default, root is set to false
• If a collection has been set to be root, it will be pulled out from it's filesystem tree location in the navigation to root. It should not be rendered in its original location.
• If there are no non-root collections or no entities left in the default tree, then only the title should not be rendered. E.g. the usecase when I have src/components and src/pages collections and both have been set to be root.

WDYT?

[paulrobertlloyd]

As the person responsible for opening this issue, I guess I should comment.

While it’s great to see these old feature requests get resolved, I haven’t used Fractal in years, so have zero context – or recall – regarding this issue. So, please do go ahead without me. 🙂

[mihkeleidast]

Ah don't worry about it - the issue is still open because it looks like a great improvement. The proposal was not directed at you, rather at my co-maintainers. I find it's better to talk through the proposals before diving into code :)

[LeBenLeBen]

@mihkeleidast I guess that would work and without requiring any breaking change for a first version.

If we rather want that for the next major version, a single folder (no more components VS docs) that contains the whole tree might be better in the sense that the file system and the UI are perfectly aligned all the time.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.