_____ _ _____ _ | | |_|___| | |_|___ _ _ ___ ___ ___ ___ ___ | | |_ -| | | | _| | |_ -| | -_|_ -|_ -| |__|__|_|___|\___/|_|_| |___|___|_|_|___|___|___|
// Runtime Page Generation
This website's design is powered by a custom-built just-in-time static site generator (JIT SSG). While the system could easily be adapted to generate an excessive number of HTML pages, it instead generates pages dynamically from text files based on the URL slug requested. This approach reduces disk space, simplifies backup and archiving, and makes content deployment relatively instantaneous.
// General Concept
The system is designed to prioritize and emphasize the backend. The overall design is meant to emulate the feel of Angelfire websites circa 1998, mixed with a web-based TUI rendered in HTML. With a retro text-based design, dynamic page generation and hVmark parsing in milliseconds, the server keeps plenty of headroom for what actually matters: traffic handling, firewall operations, and uptime integrity.
// hVmark
hVmark is the lightweight markup language designed specifically for this site. It was created because I like Markdown in theory more than in practice. hVmark makes writing more efficient and produces clean, consistent HTML for long-term maintenance and posterity.
By design, hVmark doesn't work on lines already containing HTML. If you check the source of a page written in hVmark, you’ll notice how multi-line HTML snippets are collapsed into single lines. That's because any hard-coded HTML must be isolated to single lines for stability and organization.
Pages and posts bend to the will of hVmark, not the other way around. If a layout breaks because of code, then the content must be adjusted, not the parser. The overall goal is to keep the parser lean, responsive, and free of any bloat caused by edge cases. In short: hVmark is meant to be worked around when necessary, not endlessly extended.
// Future Plans
Development is continuous, but not on a set schedule or roadmap. Changes occur as new ideas surface, or existing systems emphatically demand refinement. Features are added only if they strengthen the site’s autonomy, accessibility, efficiency, or decipherability. And if I feel like adding something because I felt like it at the time.
EOF // Return code: 0