How It Works
The whole process on one page: how a template turns into files in your project. For what happens inside each step, how a single file is processed and how to choose the way a file is written, see Under the Hood.
The big picture
A template is a folder in your project. You pick it from a menu, answer a form, review the result and finish. Nothing is written until the last step.
- A template is plain files, so it lives in Git with your code. See Core Principles and Template Basics.
- The four steps are described in the Generation Workflow. The form is step 1, the log is step 2, the preview is step 3 and the write is step 4.
- Your values are remembered per template: see History.
Where to read more
- Getting Started - Install the plugin and generate your first files
- Under the Hood - What happens inside each step, and how a file is processed
- All Features - Every feature, each with a link
- Template Basics - How a template is written
- Advanced Templates - Mapping, loops,
seed,insertand more