Closed hollowaykeanho closed 1 year ago
templates
namespace is freed up for content templating purposes. The existing directory was renamed to outputs
which is more appropriate.
We will begin developing content templates moving forward using this route and set templates
directory as public API.
Come to think of it, we shouldn't facilitate such templates feature here but to set it as independent module (e.g. a separate git). Page content template is entirely different context and squeezing it into the primary engine can make the project very bloated. Hence, let's not include it.
Closing this issue as will not implemnet.
Description
Develop a templater way (e.g.
express 'Hestia/content/store-product.html' .
) to facilitate and archive content paging design. Ensures these content templates can import the necessary components seamlessly.Expected Behavior
A function capable of quickly render a page content.
Current Absent Behavior
content templating currently only limited to project-specific repository.
Attachment