-
-
- Markdown support with an @-directive +
- Stress-test seggies (maybe build a large "stresstest" project that uses the most cursed possible permutations of all the sitix features).
- Safety: Sitix should not delete your entire codebase if you accidentally mistype the command.
- Use Evals more widely and implement string manipulation.
iterator variable will be, for every item,
the referenced array element. Note: When iterating over a directory, every file will be given a filename property! This can be used like
\[f directory i]\[^i.filename]\[/], which would spew out the filenames of every file in that directory.
- \[@command option]: Set a file-specific flag. File-specific flags are used to do things like minify text. At the moment, the only valid @-commands
- are \[@on minify], which enables minifier for the file, and \[@off minify], which disables minifier. Minifier simply reduces chains of whitespace
- to a single whitespace. In the future, \[@on markdown] and \[@off markdown] will allow Markdown-like processing across the file.\[@command option]: Set a file-specific flag. File-specific flags are used to do things like minify text. For example, the minifier is controlled by
+ \[@on minify], which enables minifier for the file, and \[@off minify], which disables minifier. Minifier simply reduces chains of whitespace
+ to a single whitespace. \[@on markdown] and \[@off markdown] allow Markdown-like processing across the file. Sitix Markdown is not quite ready
+ for widespread use, yet, but at the time of writing supports *italic*, **bold**, __underline__, ~~strikethrough~~, `code`, and automatic paragraphs/line breaks.
+ It works quite nicely with minifier, yes.There are a number of "special objects" that resolve magically at different places. The most useful two are
__after__ and __before__,