We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi @matuzo
With your permission, I'd like to separate layout templates into their own root _layouts folder, so that we get the following structure:
_layouts
hell/ - _includes/ - _layouts/
…rather than the existing structure we have now:
hell/ - _includes/ - layouts/
This was an optional configuration released in Eleventy 0.8.0.
The reason I'm suggesting this change… I want to suggest we start using includes from within layouts, so that we have a nice clean way to handle:
includes
<head>
<body>
But also, when I went looking for the layouts folder, I didn't expect to see it inside of _includes. (maybe that's my Rails experience showing :P)
layouts
_includes
Waddayathink? -S
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi @matuzo
With your permission, I'd like to separate layout templates into their own root
_layouts
folder, so that we get the following structure:…rather than the existing structure we have now:
This was an optional configuration released in Eleventy 0.8.0.
The reason I'm suggesting this change… I want to suggest we start using
includes
from within layouts, so that we have a nice clean way to handle:<head>
markup includes for:<body>
markup includes:But also, when I went looking for the
layouts
folder, I didn't expect to see it inside of_includes
. (maybe that's my Rails experience showing :P)Waddayathink?
-S
The text was updated successfully, but these errors were encountered: