I'm assuming you define a file system structure using filenames and indentation, with names ending with a / meaning a directory, and content indented under a filename meaning the file contents. But it actually took me several takes to correctly read the indentation.
The result is a kind of text-only zip archive? That's not very helpful.
Actual templates have substitutions, like you enter the name of your project and that's used in the text of the files. You could do that as a preprocessing step, I guess, but what's the point? Also it will be hard to ensure the integrity of the archive if you do simple textual substitutions.
Also I'm pretty sure from the code that you can just make an archive like this:
> Actual templates have substitutions, like you enter the name of your project and that's used in the text of the files.
You could have a settings file in your template for those substitutions. For example:
stamp
settings.scroll
replace TITLE My Blog
replace AUTHOR Breck Yunits
index.scroll
import settings.scroll
title TITLE
author AUTHOR
import footer.scroll
footer.scroll
import settings.scroll
You are reading TITLE
I'm assuming you define a file system structure using filenames and indentation, with names ending with a / meaning a directory, and content indented under a filename meaning the file contents. But it actually took me several takes to correctly read the indentation.
The result is a kind of text-only zip archive? That's not very helpful.
Actual templates have substitutions, like you enter the name of your project and that's used in the text of the files. You could do that as a preprocessing step, I guess, but what's the point? Also it will be hard to ensure the integrity of the archive if you do simple textual substitutions.
Also I'm pretty sure from the code that you can just make an archive like this: