Guide · Framework
Deploy Jekyll to Novence
jekyll build writes ./_site. npx novence deploy ./_site. Ruby build stays on your machine.
Jekyll is a static compiler. Novence only needs _site. GitHub Pages, jekyll serve, and GitHub Actions are optional; the host does not run Ruby.
Configure
Use directory permalinks (/:title/) so output is title/index.html. Set url to the live origin after the first deploy. Keep baseurl empty unless you truly serve under a subpath (Novence sites are origin-rooted).
Plugins run at build time. Anything that needs a request-time server is incompatible.
# _config.yml
url: "https://{suffix}.novence.ai"
baseurl: ""
permalink: /:categories/:title/Build
bundle exec jekyll build
bundle exec jekyll build (or jekyll build). Confirm _site/index.html. Incremental builds are local convenience only.
Deploy
npx novence deploy ./_site
npx novence deploy ./_site. Pass the path if dist / public would be auto-detected first.
The CLI auto-detects ./_site among dist, build, out, public, _site. Pass the path if another of those folders exists. Full CLI: /cli.
Caveats
- Do not upload the Jekyll source tree (
_posts,_layouts). Upload_site. - GitHub Pages–only plugins are fine if they run during your local or CI build.
- Node is only required for the Novence CLI (
npx), not for Jekyll itself.
FAQ
Is this a replacement for GitHub Pages?
For static Jekyll output, yes — with an API/CLI/MCP control plane instead of git push to gh-pages. See /vs/github-pages.
Can I use GitHub Actions?
Yes. Build _site in CI, set NOVENCE_API_KEY, then npx novence deploy ./_site --no-input --json.
What about GitHub Pages collections?
They compile during jekyll build. The host only sees HTML and assets.
Agents ship. Novence hosts.
Copy Prompt or get a key. Then npx novence deploy ./_site.