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 to define an input folder #105

Open
iagobruno opened this issue Dec 6, 2019 · 4 comments · May be fixed by #106
Open

Feature Request: Allow to define an input folder #105

iagobruno opened this issue Dec 6, 2019 · 4 comments · May be fixed by #106

Comments

@iagobruno
Copy link

iagobruno commented Dec 6, 2019

Current Behavior

Zero pick up files and folders in the project root folder, this is ok for small projects but can get messy for sites with many pages. Look at this:

image

Proposal

Allow to define an input folder where Zero will get the files, for example:

zero src
zero src/pages // or
zero ../client/pages // or
zero src docs // Multiple entry points, maybe 👀 

And so the spread files can be organized into a "src" folder like that:

image

This also solves the confusion in .zeroignore to route only the desired files.

Backward compatibility

This new behavior can be easily integrated without breaking old projects. If no entry point is specified, it will fallback to root folder as usual.

@asadm
Copy link
Contributor

asadm commented Dec 7, 2019

Although not documented (I think), this should already work. Doing zero src or zero www or even zero build www should work just fine. Give it a shot please and see if you find it good enough to be added to docs.

Here is how I organize zeroserver.io:

Screen Shot 2019-12-07 at 9 28 52 AM

And run it with zero www.

@iagobruno
Copy link
Author

I searched in the docs before open this issue but did not find this information 😓.
It would be relevant to show this. Wait a minute...

@iagobruno iagobruno linked a pull request Dec 7, 2019 that will close this issue
@asadm
Copy link
Contributor

asadm commented Dec 7, 2019

@iagobruno Did it work fine for your project?

@iagobruno
Copy link
Author

Yes, much better than the other solution I used in another project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants