Vic's cyber space.
▸ _esnext/ # Compiled ESNEXT browser scripts
▸ _includes/ # Layouts, templates, and source CSS and TS files
▸ _site/ # The static build of the site
▸ _spacephantom/ # Special directory hosting the Space Phantom game
▸ _temp/ # Generated locally when compiling programs, for diffing checksums
▸ assets/ # Images and other static assets
▸ filters/ # Filters for text content such as language detectors
▸ plugins/ # Server plugins for Lume, such as the program compiler and CSS bundler
▸ posts/ # These are the markdown files that contain the content of the site
▸ processors/ # Processors for posts, such as the HTML image markup optimizer
404.vto # 404 page, shown on path misses
_bundle.css # Bundled CSS file, contains all styles inline
_config.ts # Registers, plugins, processors, filters, and other configs
index.md # Home page
README.md # This file
server.ts # Server setup
*.(md|vto) # Pages, such as the weblogInstall Deno and run deno task serve to launch watch mode.
Follow Lume documentation to modify layouts, templates, processors, plugins and more.
CSS stylesheets are bundled and minified with LightningCSS on build and inlined with the base layout.
The source .css files can be found in the _includes/css directory. Bundled styles are generated as _bundle.css.
Programs are compiled from Typescript into ESNext on build, in order to be delivered inline from server with the document.
Source .ts files can be found in the _includes/ts folder. Compiled files are stored in the _esnext directory. Here's an example of a layout using compiled files.
Programs are written in my own functional dialect and might look a bit unlike typical DOM manipulators. Why? Because it's fun. 😈
The compiler and bundler plugins perform checksum comparisons to rerun on watch mode in order to reload changes live. In the compiled programs case, an untracked directory _temp/esnext is created as a part of this diffing process.
MIT License
Copyright (c) 2024 Victor René Molina Rodriguez