Page
About Siteforge
Siteforge separates content, themes, and site-operation output so content sites, product pages, docs, and agents are easier to maintain.
Why Siteforge exists
Most content sites do not need a new frontend project every time. They need a stable content directory, reusable theme boundaries, basic SEO, sitemap, feed, search, privacy preferences, and discovery resources that agents can read.
Siteforge moves that repeated work into a static builder. Site-level information lives in config.yml, content lives in content/, themes live in themes/<name>/, and output goes to dist/.
Who it is for
- Developers who like the Hexo mental model but want clearer theme boundaries.
- Open-source projects or small teams publishing product pages, docs, and ordinary pages.
- People who want Codex, Claude, or other agents to understand and extend the site quickly.
This site
This site introduces Siteforge itself: why it exists, how to use it directly, how content and docs are organized, and how to extend it through theme boundaries. The footer links to this showcase theme source so the site can be reused or adapted.
License and attribution
Siteforge is released under AGPL-3.0-or-later. Modified, distributed, publicly deployed, or derivative versions should keep the corresponding source open under AGPL requirements.
This theme is built on Siteforge. Theme source: jsw-teams/siteforge-showcase-theme. Upstream Siteforge: jsw-teams/siteforge. Public NOTICE: /NOTICE.