I'd like to introduce new structure for nunjucks templates.
For now, we usually have base(atoms), components, and pages are generated from any .nunj in tpl folder.
So, e.g. if you want to see the component you are working on, you also have to create a page which has this component. Because .nunj files from other folders that are inside tpl are not being converted to .html.
What if we compiled all of the actual nunjucks templates and show them in index.nunj file like:
atoms:
components:
pages:
- homepage
- contact
- products
So that we could see all the parts in the index.nunj. What do you think?
I'd like to introduce new structure for nunjucks templates.
For now, we usually have base(atoms), components, and pages are generated from any
.nunjin tpl folder.So, e.g. if you want to see the component you are working on, you also have to create a page which has this component. Because
.nunjfiles from other folders that are inside tpl are not being converted to.html.What if we compiled all of the actual nunjucks templates and show them in
index.nunjfile like:atoms:
components:
pages:
So that we could see all the parts in the
index.nunj. What do you think?