Brainstorm on how to make archetypes work easily and allow both users and themes to add them:
A new conventional archetypes folder should be used
Can be adjusted to a different name using settings (like other paths)
More archetypes folders can be added
A command new should be added
When the new command is used, a separate series of pipelines will be run that finds archetypes and evaluates the right one
The new command takes the name of an archetype (derived from file name, case-insensitive)
The archetypes folders contains documents of any supported templating type along with metadata (just like normal documents)
The archetypes pipeline finds and evaluates the correct archetype document and renders it with any settings --settings key=value - the full bootstrapper and configuration files should be evaluated so we know things like input folder
This lets the user specify any metadata the archetype document needs
The archetype document can use whatever .Get...() methods, shortcodes, etc. it needs to
Theme and theme extensions can have a archetypes folder right next to their input folder to define archetypes
Brainstorm on how to make archetypes work easily and allow both users and themes to add them:
archetypesfolder should be usednewshould be addednewcommand is used, a separate series of pipelines will be run that finds archetypes and evaluates the right onenewcommand takes the name of an archetype (derived from file name, case-insensitive)--settings key=value- the full bootstrapper and configuration files should be evaluated so we know things like input folder.Get...()methods, shortcodes, etc. it needs toarchetypesfolder right next to theirinputfolder to define archetypes