Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
paulrobertlloyd opened this issue Jul 28, 2016 · 2 comments

Comments

Projects
3 participants
@paulrobertlloyd
Copy link
Contributor

commented Jul 28, 2016

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:

screen shot 2016-07-28 at 10 51 56

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

screen shot 2016-07-28 at 10 51 22

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

This comment has been minimized.

Copy link

commented Jun 5, 2017

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

@allmarkedup allmarkedup added this to the 2.0 milestone Aug 3, 2017

@allmarkedup allmarkedup added the v2.x label Aug 7, 2017

@allmarkedup allmarkedup added this to Inspector in [v2] Fractal Core Aug 7, 2017

@allmarkedup allmarkedup moved this from Inspector to Fractal core in [v2] Fractal Core Aug 7, 2017

@allmarkedup allmarkedup moved this from Planning to In progress in [v2] Fractal Core Aug 16, 2017

@allmarkedup allmarkedup moved this from In progress to Completed in [v2] Fractal Core Sep 1, 2017

@stale

This comment has been minimized.

Copy link

commented Jul 13, 2018

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.

@stale stale bot added the wontfix label Jul 13, 2018

@stale stale bot closed this Jul 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.