Sitix is a universal preprocessor. HTML? Of course. CSS? Yep! JavaScript? Certainly! Sitix will template and preprocess anything, whether it be a nice simple HTML file or a hand-edited GIF from 1998. Say goodbye to annoying configuration discrepancies between CSS and HTML and JavaScript - just throw your shared config in a config.stx file and let Sitix do the rest!
+
Sitix is a universal preprocessor. HTML? Of course. CSS? Yep! JavaScript? Certainly! Sitix will template anything, whether it be a nice simple HTML file or a hand-edited GIF from 1998. Say goodbye to annoying configuration discrepancies between CSS and HTML and JavaScript - just throw your shared variables in a config.stx file and let Sitix do the rest!
-
No more restrictive project structures, irritating configuration files, or magic. Goodbye Ruby, "blog-awareness", difficult configuration, and bulky outputs. Sitix renders what you want, when you want it, and doesn't ask questions.
Like what you see? install Sitix and start building modern websites now!
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
\ No newline at end of file
+
No more restrictive project structures, irritating configuration files, or magic. Goodbye Ruby, "blog-awareness", difficult configuration, and bulky outputs. Sayonara obtuse frameworks, inefficient CSR, and annoying configuration. Sitix renders what you want, when you want it, and doesn't ask questions.
Like what you see? install Sitix and start building modern websites now!
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
\ No newline at end of file
diff --git a/output/pages/about.html b/output/pages/about.html
index ef39eb9..80f7bd1 100644
--- a/output/pages/about.html
+++ b/output/pages/about.html
@@ -1,8 +1 @@
-
-
-
- Sitix | About
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
Sitix began in Summer '23 when I got fed up with the quirks of Jekyll and decided to build my own templating engine. I put together a schematic not unlike modern Sitix and began implementing it in Rust (which I had just learned), but I quickly realized that my pattern was simply not going to work for such a complex design, and so after a lot of fruitless debugging and such I eventually stopped developing it. It's probably still up here. In November '24 I was working on a client's website and, once again, got fed up with Jekyll. I remembered the Sitix project I'd begun in 2023 and tried to implement it - but failed spectacularly. Sitix was a shipwreck. So, through early March, I reimplemented: I moved to C++, a much more familiar language; changed the structure to be just quirky enough to satisfy me while still robust and usable, and quickly got Sitix behind several websites.
Sitix is designed to replace everything I like about Jekyll (Liquid. It's just Liquid. I hate literally everything else), while also providing a saner interface, and being much easier to compile and install (farewell, Gem Hell). I also incorporated concepts from JavaScript (especially JSON); parts of the object model are obviously inspired by JavaScript, and the tree-like structure of a Sitix file is heavily remnant of JSON. I also added a little of my own "charm"; evident in the scope system (which is even less sane than JavaScript's) and the not-quite-XML tag structure.
Sitix is a very young project, and I'm still working out the bugs and adding crucial features. The stuff I'm working on is usually going to be near the top of the TODO list.
Sitix is protected by GNU GPLv3. Please put a little "built with Sitix by Tyler Clarke" with a link to this website somewhere on every Sitix-generated page you make (Sitix can make this easy with templates :D), if you choose to use Sitix.
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
\ No newline at end of file
diff --git a/output/pages/install.html b/output/pages/install.html
index f2c0c1e..4939354 100644
--- a/output/pages/install.html
+++ b/output/pages/install.html
@@ -1,14 +1,19 @@
- Sitix | Install Sitix
+ Sitix is written in C++ without any frameworks or anything. It doesn't muck about with Node.JS or Ruby or any such stuff. This means native-level performance,
+ but requires compilation and testing on many platforms. It's guaranteed to work on Fedora Linux and probably works in most other Linuxes;
+ MacOS is a possibility. Windows, being too stone-age for POSIX, probably won't be able to run Sitix.
At the moment, Sitix has no prebuilt binaries; I hope to include RPM/DEB packages in the next release. To install it, you'll need to clone
the Github repository, run ./build.sh, and (assuming the build completes successfully)
copy the generated sitix binary to some PATH-accessible location (/usr/bin is a good bet). Sitix requires a C++20-compatible
- G++ installation; it has no other dependencies. Sitix is theoretically cross-compilable to Windows, but I have no intention of ever officially supporting Windows.
+ G++ (usually included with the gcc package); it has no other dependencies. Sitix is theoretically cross-compilable to Windows, but I have no intention of ever officially supporting it;
+ Microsoft doesn't deserve it.
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
\ No newline at end of file
diff --git a/output/pages/noteboard.html b/output/pages/noteboard.html
new file mode 100644
index 0000000..e3a6af0
--- /dev/null
+++ b/output/pages/noteboard.html
@@ -0,0 +1 @@
+ Sitix | Noteboard
This is where I'll post miscellaneous notes on Sitix stuff. If you're using Sitix (or just interested in the project), you should check back here periodically for information on new releases, design considerations, known bugs, etc. You can think of it as a miniblog.
2024-3-9: The stupid "Something has gone terribly wrong" warning is NOT important; you can safely ignore it. It's just debugging information pour moi.
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
\ No newline at end of file
diff --git a/output/pages/todo.html b/output/pages/todo.html
index 7a70a82..55522ab 100644
--- a/output/pages/todo.html
+++ b/output/pages/todo.html
@@ -1,7 +1,8 @@
- Sitix | Todo
Sitix is still a pretty young piece of software, so if there's a missing feature that isn't on this list, don't hesitate to submit a feature request on the issues page.
Alternatively, you could just write it yourself! This TODO list is mostly for my memory, but I would love codebase contributions to get some things crossed off.
@@ -12,6 +13,8 @@
Code cleaning (need to fix memory management especially)
Make config less hack (move from [i config] to [i exists], and create empty objects on global with -c)
Add an unpack/ghost operator so setting objects to other objects works (something like [=ghostingName-] [%ghostedObject] [/])
+
Safety: Sitix should not delete your entire codebase if you accidentally mistype the command.
+
Get rid of that stupid "something has gone terribly wrong" warning. It's not a problem, it's just an artefact of an old debugging marathon.
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
\ No newline at end of file
diff --git a/output/pages/usage.html b/output/pages/usage.html
new file mode 100644
index 0000000..c4e0ef9
--- /dev/null
+++ b/output/pages/usage.html
@@ -0,0 +1,58 @@
+
+
+
+
+ Sitix | Usage
+ Sitix is a KISS program, so there's not a lot of setup. Once you've got it installed (see for information on that),
+ you need a project to build. The simplest Sitix project structure is just a site folder, which contains the actual Sitix "scripts". When
+ (you absolutely must be outside of the site directory to do this!) you run sitix site, Sitix will delete the output directory
+ and all contents, if it exists, and then create a new output directory for the compiled site code. Then, Sitix will walk down the tree of
+ your site directory, creating appropriate subdirectories and directly copying over any file that doesn't have an opening phrase - [!],
+ for a Sitix page, or [?] for a data page (which will not be rendered itself, but may be used for templating or configuration). The opening phrase
+ MUST be the first three bytes of the file; if there are any whitespaces before it, the file will be treated as plain data. If you want
+ it to render to a different directory, pass the -o location flag.
+
+
+ WARNING: -o is very dangerous! If you tell Sitix to render to a directory with important information in it, that directory is as good as gone.
+ At the moment Sitix does not put any effort into questioning your choices, so make sure to double-check everything is okay before running any sitix command! Avoiding
+ -o unless you really need it is generally a good policy.
+
+
+ Let's cover some syntax. All Sitix commands are enclosed in brackets like [command] (you can escape brackets with backslashes). There aren't very many
+ Sitix commands; at the moment, it's just:
+
+
[=variableName variableContent]: This simply sets variableName to be equal to variableContent at that point on the scope tree.
+
[=variablename-]variableContent[/]: The expanded form of above. This allows for much more complicated variables, including variables containing
+ Sitix commands (in the compressed form, anything inside MUST be plaintext). It's generally preferred to use this when the content is more than a word or two.
+
[^variableName]: "Dereferences" a variable, forcing it to render. If that variable contains other variables (like [=parent-] [=child-] content [/] [/]),
+ the child variables will NOT be rendered, but if variables with the same name as the children exist at some point in the parent tree of the dereferenced variable exist, they will be replaced.
+ Variables at the dereferencing position will NOT be replaced.
+
[#filename]: Dereferences a Sitix file (or plain file, which would just copy over content without processing it) at this position. The filename must be relative
+ to the root directory (usually the site directory), rather than the directory the including file is stored in. This is very useful for templating.
+
[i request <...>][e][/]: This is an if condition. If in Sitix contains an object (between the [i] and either [/] or [e]) that will
+ be rendered if the condition evaluates to "true", and, optionally (between [e] and [/]), an object that will be rendered if the condition is false.
+ Requests can be,
+
+
config configName: Check whether or not a command-line config switch is enabled (you can enable them with -c configName).
+
equals variable1 variabl2: Check whether two variables are the same (the check is flawed, but pretty good. See the relevant section in main.cpp
+ for information on this.)
+
exists variable: Check whether a variable exists. Good for simple boolean flags.
+
+
+
[f array iterator]: For loop that iterates over an array (note: in Sitix, every subdirectory of the root dir can be treated as
+ an array of objects, each object being a file! This allows things like generating blog links). The 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.
+
+ 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.
+ And that's it! To see how these are used creatively in the wild, check out the source code for this website.
+
+
+ For a more thorough look at Sitix, check out the source code. There's a rather large comment at the start of
+ main.cpp that provides a deep look at Sitix syntax and usage.
+
Information Sitix (including this website) is open-sourceFree Software protected by GNU GPLv3. Looking to contribute? The source code for this website is hosted on Github, as is Sitix itself. Sitix is still young and probably buggy; if you have issues, submit a bug report at the issues page or contact me at plupy44@gmail.com (github issue preferred). If you want to contribute, but don't know where to start, see The Todo List.
Site designed by Tyler Clarke and built with Sitix. This page uses the Lato fonts.
No more restrictive project structures, irritating configuration files, or magic. Goodbye Ruby, "blog-awareness", difficult configuration, and bulky outputs.
+ Sayonara obtuse frameworks, inefficient CSR, and annoying configuration.
Sitix renders what you want, when you want it, and doesn't ask questions.
- About Page (TODO)
+ Sitix began in Summer '23 when I got fed up with the quirks of Jekyll and decided to build my own templating engine. I put together a schematic not unlike
+ modern Sitix and began implementing it in Rust (which I had just learned), but I quickly realized that my pattern was simply not going to work for such a complex
+ design, and so after a lot of fruitless debugging and such I eventually stopped developing it. It's probably still up here.
+ In November '24 I was working on a client's website and, once again, got fed up with Jekyll. I remembered the Sitix project I'd begun in 2023 and tried to implement it
+ - but failed spectacularly. Sitix was a shipwreck. So, through early March, I reimplemented: I moved to C++, a much more familiar language; changed the structure to be
+ just quirky enough to satisfy me while still robust and usable, and quickly got Sitix behind several websites.
+ Sitix is designed to replace everything I like about Jekyll (Liquid. It's just Liquid. I hate literally everything else), while also providing a saner interface,
+ and being much easier to compile and install (farewell, Gem Hell). I also incorporated concepts from JavaScript (especially JSON); parts of the object model are
+ obviously inspired by JavaScript, and the tree-like structure of a Sitix file is heavily remnant of JSON. I also added a little of my own "charm"; evident
+ in the scope system (which is even less sane than JavaScript's) and the not-quite-XML tag structure.
+ Sitix is a very young project, and I'm still working out the bugs and adding crucial features. The stuff I'm working on is usually going to be near the top of
+ the TODO list.
+ Sitix is protected by GNU GPLv3. Please put a little "built with Sitix by Tyler Clarke" with a link to this website somewhere on every Sitix-generated page
+ you make (Sitix can make this easy with templates :D), if you choose to use Sitix.
[/]
[#templates/default.html]
\ No newline at end of file
diff --git a/site/pages/install.html b/site/pages/install.html
index 1846493..42199ad 100644
--- a/site/pages/install.html
+++ b/site/pages/install.html
@@ -1,11 +1,16 @@
[!]
[=title Install Sitix]
+[=isSimple ]
[=content-]
+ Sitix is written in C++ without any frameworks or anything. It doesn't muck about with Node.JS or Ruby or any such stuff. This means native-level performance,
+ but requires compilation and testing on many platforms. It's guaranteed to work on Fedora Linux and probably works in most other Linuxes;
+ MacOS is a possibility. Windows, being too stone-age for POSIX, probably won't be able to run Sitix.
At the moment, Sitix has no prebuilt binaries; I hope to include RPM/DEB packages in the next release. To install it, you'll need to clone
the Github repository, run ./build.sh, and (assuming the build completes successfully)
copy the generated sitix binary to some PATH-accessible location (/usr/bin is a good bet). Sitix requires a C++20-compatible
- G++ installation; it has no other dependencies. Sitix is theoretically cross-compilable to Windows, but I have no intention of ever officially supporting Windows.
+ G++ (usually included with the gcc package); it has no other dependencies. Sitix is theoretically cross-compilable to Windows, but I have no intention of ever officially supporting it;
+ Microsoft doesn't deserve it.
Once you've got Sitix installed, see Usage.
diff --git a/site/pages/noteboard.html b/site/pages/noteboard.html
new file mode 100644
index 0000000..86bbed1
--- /dev/null
+++ b/site/pages/noteboard.html
@@ -0,0 +1,13 @@
+[!][@on minify]
+[=title Noteboard]
+[=isSimple ]
+[=content-]
+
+ This is where I'll post miscellaneous notes on Sitix stuff. If you're using Sitix (or just interested in the project), you should check back here
+ periodically for information on new releases, design considerations, known bugs, etc. You can think of it as a miniblog.
+
+
+ 2024-3-9: The stupid "Something has gone terribly wrong" warning is NOT important; you can safely ignore it. It's just debugging information pour moi.
+
+[/]
+[#templates/default.html]
\ No newline at end of file
diff --git a/site/pages/todo.html b/site/pages/todo.html
index a51e027..8b78575 100644
--- a/site/pages/todo.html
+++ b/site/pages/todo.html
@@ -1,5 +1,6 @@
[!]
[=title Todo]
+[=isSimple ]
[=content-]
Sitix is still a pretty young piece of software, so if there's a missing feature that isn't on this list, don't hesitate to submit a feature request on the issues page.
@@ -11,6 +12,8 @@
Code cleaning (need to fix memory management especially)
Make config less hack (move from \[i config] to \[i exists], and create empty objects on global with -c)
Add an unpack/ghost operator so setting objects to other objects works (something like \[=ghostingName-] \[%ghostedObject] \[/])
+
Safety: Sitix should not delete your entire codebase if you accidentally mistype the command.
+
Get rid of that stupid "something has gone terribly wrong" warning. It's not a problem, it's just an artefact of an old debugging marathon.
+ Sitix is a KISS program, so there's not a lot of setup. Once you've got it installed (see for information on that),
+ you need a project to build. The simplest Sitix project structure is just a site folder, which contains the actual Sitix "scripts". When
+ (you absolutely must be outside of the site directory to do this!) you run sitix site, Sitix will delete the output directory
+ and all contents, if it exists, and then create a new output directory for the compiled site code. Then, Sitix will walk down the tree of
+ your site directory, creating appropriate subdirectories and directly copying over any file that doesn't have an opening phrase - \[!],
+ for a Sitix page, or \[?] for a data page (which will not be rendered itself, but may be used for templating or configuration). The opening phrase
+ MUST be the first three bytes of the file; if there are any whitespaces before it, the file will be treated as plain data. If you want
+ it to render to a different directory, pass the -o location flag.
+
+
+ WARNING: -o is very dangerous! If you tell Sitix to render to a directory with important information in it, that directory is as good as gone.
+ At the moment Sitix does not put any effort into questioning your choices, so make sure to double-check everything is okay before running any sitix command! Avoiding
+ -o unless you really need it is generally a good policy.
+
+
+ Let's cover some syntax. All Sitix commands are enclosed in brackets like \[command] (you can escape brackets with backslashes). There aren't very many
+ Sitix commands; at the moment, it's just:
+
+
\[=variableName variableContent]: This simply sets variableName to be equal to variableContent at that point on the scope tree.
+
\[=variablename-]variableContent\[/]: The expanded form of above. This allows for much more complicated variables, including variables containing
+ Sitix commands (in the compressed form, anything inside MUST be plaintext). It's generally preferred to use this when the content is more than a word or two.
+
\[^variableName]: "Dereferences" a variable, forcing it to render. If that variable contains other variables (like \[=parent-] \[=child-] content \[/] \[/]),
+ the child variables will NOT be rendered, but if variables with the same name as the children exist at some point in the parent tree of the dereferenced variable exist, they will be replaced.
+ Variables at the dereferencing position will NOT be replaced.
+
\[#filename]: Dereferences a Sitix file (or plain file, which would just copy over content without processing it) at this position. The filename must be relative
+ to the root directory (usually the site directory), rather than the directory the including file is stored in. This is very useful for templating.
+
\[i request <...>]\[e]\[/]: This is an if condition. If in Sitix contains an object (between the \[i] and either \[/] or \[e]) that will
+ be rendered if the condition evaluates to "true", and, optionally (between \[e] and \[/]), an object that will be rendered if the condition is false.
+ Requests can be,
+
+
config configName: Check whether or not a command-line config switch is enabled (you can enable them with -c configName).
+
equals variable1 variabl2: Check whether two variables are the same (the check is flawed, but pretty good. See the relevant section in main.cpp
+ for information on this.)
+
exists variable: Check whether a variable exists. Good for simple boolean flags.
+
+
+
\[f array iterator]: For loop that iterates over an array (note: in Sitix, every subdirectory of the root dir can be treated as
+ an array of objects, each object being a file! This allows things like generating blog links). The 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.
+
+ 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.
+ And that's it! To see how these are used creatively in the wild, check out the source code for this website.
+
+
+ For a more thorough look at Sitix, check out the source code. There's a rather large comment at the start of
+ main.cpp that provides a deep look at Sitix syntax and usage.
+
