Skip to content

octospacc/staticoso

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Development has been moved

This branch is now frozen and won't receive any updates. For now, all future development will happen on the new Dev monorepo branch: https://gitlab.com/octtspacc/staticoso/-/tree/Dev.

The main branch remains indefinitely as it is to not break build workflows. However, everyone is advised to adjust their workflows ASAP. Consult the README on the Dev branch for more details.


staticoso (from Italian statico [static] + coso [thingy]) is an unpretentious static site generator.

I'm making this because I need a simple and kind-of-minimal program to serve me as a static site generator with (limited) mixed-CMS+Wiki features. Just the ones I need, of which some are unique, however.

This won't replace any of the big projects out there that do the same thing but, as all of my projects, I'm releasing it as free libre software, in the hope that someone would find it useful.
Also, this software is needed for someone to edit and compile my personal website sitoctt from its source. Being that site too released under a libre license that allows modifications, I have to also release the tools I use to build it, or really people will never be able to make the most out of it.

Everything is still kind of a WIP, and some bugs might appear across commits, but feel free to experiment with all of this stuff! If you really want to use this tool for your website, I suggest you don't do like I do in my build process, running always with the latest code commit; instead, either download a snapshot of the code and keep that, or always clone from a specific commit, until you have time when I do an update to check if your site actually builds correctly with the new version.

Documentation

Documentation can be found at octtspacc.gitlab.io/staticoso-docs.
Obviously, it's built with staticoso itself 😁️. Its source repo can be found at gitlab.com/octtspacc/staticoso-docs.

Keep in mind that, currently, it's still very incomplete. Any help, from writing the documentation to creating a decent HTML+CSS template for its site, is more than welcome.

Dependencies

Optional dependencies

Needed for Pug input support:

Needed for Gemtext output support:

Features roadmap

  • Generation of simplified pages compliant with the HTML Journal standard
  • HTML feeds (pages with list of N most recent posts)
  • Lists of all pages in a site directory
  • Page redirects / Alt URLs (+ ActivityPub URL overrides)
  • Progress bars for the build process!
  • Multithreading
  • Differential building
  • Overriding internal HTML snippets for template-specific ones
  • Static syntax highlighing for code blocks in any page
  • File name used as a title for pages without one
  • Custom category names in header links
  • Choosing custom name for Blog and Uncategorized categories
  • Choosing to use a template for all pages in a folder/category
  • Configuration with both INI files and CLI arguments
  • Category-based feeds
  • Support for multi-language sites
  • The title attribute is added to images which only have alt (for desktop accessibility), or viceversa
  • Local (per-page) and global (per-site) macros
  • ActivityPub (Mastodon) support (Feed + embedded comments)
  • Polished Gemtext generation
  • Autodetection of pages and posts
  • Info for posts shown on their page
  • HTML and CSS minification for Pages and Assets
  • Full Open Graph support
  • Custom categories for posts
  • Custom static and dynamic page parts
  • Showing creation and modified date for posts
  • Generation of category pages (ex. page with list of blog posts)
  • Custom and automatic page sorting
  • SCSS compilation support for CSS templates
  • Pug support for base templates and page side parts
  • Hot-recompile (for website development)
  • TXT sitemap generation
  • Atom + RSS feed generation
  • Generation of global website menu as a tree or as a line
  • Generation of page (titles) menu as a tree
  • Auto-detection of titles in a page
  • HTML, TXT, Extended Markdown, and Pug supported as input page files

Known issues (might need further investigation)

  • Bad HTML included in Markdown files can cause a build to fail entirely.
  • Despite differential building and multithreading, the program still needs some more optimizations.
  • Ordering pages in the global menu with external configuration flags (outside the pages' source) yields broken and unpredictable results.