admin/sitix-website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update the site... again

Browse Source
This commit is contained in:
Lazy Hippopotamus
2024-03-23 14:05:22 -04:00
parent a611d01a71
commit 38e56ab21b
3 changed files with 8 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
site/pages/noteboard.html
View File

@@ -12,7 +12,8 @@
it's present in if statements and the <code>\[v]</code> directive.<br>
In other news, the program is a LOT cleaner now. Much of the processing effort has been moved into constructors and a lot of things have been simplified and
abstracted. Memory maps are now automatically unmapped and have a very pleasant buffer-like interface, and all the mapping code has been moved to a single function.<br>
The project is now ready for MarkDown!
The project is now ready for MarkDown!<br>
<b>Slightly later in the day:</b> Added markdown! It's not quite ready for production yet, but works promisingly well already.
<br><br>
<b>2024-3-11:</b> Model updates, and now this site can actually be built by the latest sitix updates :D.<br>
As of today, Sitix now leaks no memory when building this site! It took a lot of effort to trim down but it was worth it. We shall see if the luck persists.

2
site/pages/todo.html
View File

@@ -8,7 +8,7 @@
</div>
<div class="text">
<ul>
<li>Markdown support with an @-directive</li>
<li>Stress-test seggies (maybe build a large "stresstest" project that uses the most cursed possible permutations of all the sitix features).</li>
<li>Safety: Sitix should not delete your entire codebase if you accidentally mistype the command.</li>
<li>Use Evals more widely and implement string manipulation.</li>
</ul>

8
site/pages/usage.html
View File

@@ -38,9 +38,11 @@
an array of objects, each object being a file! This allows things like generating blog links). The <code>iterator</code> variable will be, for every item,
the referenced array element. <b>Note: When iterating over a directory, every file will be given a <code>filename</code> property!</b> This can be used like
<code>\[f directory i]\[^i.filename]\[/]</code>, which would spew out the filenames of every file in that directory.</li>
<li><code>\[@command option]</code>: Set a file-specific flag. File-specific flags are used to do things like minify text. At the moment, the only valid @-commands
are <code>\[@on minify]</code>, which enables minifier for the file, and <code>\[@off minify]</code>, which disables minifier. Minifier simply reduces chains of whitespace
to a single whitespace. In the future, <code>\[@on markdown]</code> and <code>\[@off markdown]</code> will allow Markdown-like processing across the file.</li>
<li><code>\[@command option]</code>: Set a file-specific flag. File-specific flags are used to do things like minify text. For example, the minifier is controlled by
<code>\[@on minify]</code>, which enables minifier for the file, and <code>\[@off minify]</code>, which disables minifier. Minifier simply reduces chains of whitespace
to a single whitespace. <code>\[@on markdown]</code> and <code>\[@off markdown]</code> 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.</li>
</ul>
You can use Sitix commands in any file with a Sitix opening phrase; Sitix commands in files that do not have an opening phrase will be ignored.<br><br>
There are a number of "special objects" that resolve magically at different places. The most useful two are <code>__after__</code> and <code>__before__</code>,