Documentation
Siteforge docs
A Siteforge path from site config and content directories to theme extension and Agent discovery.
Get started
Run the site first, then enter the theme
Siteforge follows the same practical path as many documentation sites: confirm site-level config and content directories first, then move into theme files by page type.
Direct use
Use directly
If you are writing a blog or maintaining an ordinary content site, you do not need to learn theme development first.
- Clone.
git clone https://github.com/jsw-teams/siteforge.git - Enter.
cd siteforge - Install.
npm install - Check first.
npm run checkverifies output, theme assets, and discovery resources. - Generate.
npm run generateis similar tohexo generate/hexo g. - Preview.
npm run serveris similar tohexo server/hexo s; default URL:http://127.0.0.1:4173/.
Files you usually edit
Start with config.yml: site name, languages, navigation, robots, llms, feed, discovery, and third-party scripts become structured inputs there.
Put content in content/: ordinary pages use content/pages, product docs use content/docs, and posts or mirrors continue to use their content directories.
Put theme work in themes/<name>: visual language, docs navigation, search styling, consent, lightbox, carousel, and footer behavior should be solved in the theme layer first.
Documentation