Guide · Framework

Deploy Eleventy (11ty) to Novence

npx @11ty/eleventy writes ./_site by default. npx novence deploy ./_site.

Eleventy is a plain SSG: templates in, HTML out. _site is already on the CLI auto-detect list. Serverless 11ty plugins and edge functions are out of scope for Novence.

Configure

Default output is _site. If you change dir.output, pass that folder to novence deploy. Permalinks that write about/index.html work with Novence directory URLs; about.html needs links that include the .html suffix.

Passthrough copy images, CSS, and JS into the output. Eleventy does not invent a Node server — keep it that way.

// eleventy.config.js
export default function (eleventyConfig) {
  return {
    dir: {
      input: ".",
      includes: "_includes",
      output: "_site",
    },
    htmlTemplateEngine: "njk",
    markdownTemplateEngine: "njk",
  };
}

Build

npx @11ty/eleventy

npx @11ty/eleventy (or your npm run build). Check _site/index.html. Pagination and collections are resolved at build time.

Deploy

npx novence deploy ./_site

npx novence deploy ./_site. _site is the last auto-detect candidate, so pass it if a dist or public folder also exists.

The CLI auto-detects ./_site among dist, build, out, public, _site. Pass the path if another of those folders exists. Full CLI: /cli.

Caveats

No 11ty serverless or Deno edge handlers on Novence.
Drafts excluded from the build stay off the live site until you rebuild.
Allowlisted extensions only — skip uploading .njk sources; upload _site.

FAQ

Is 11ty the same as Eleventy?

Yes. This guide is /guides/eleventy for both names.

Can I use computed data?

Yes. It runs during the Eleventy build on your machine, then the HTML is static.

What about Eleventy Image?

Build-time image transforms write files into _site. That is fine. A runtime image CDN is not provided by Novence.

Agents ship. Novence hosts.

Copy Prompt or get a key. Then npx novence deploy ./_site.

Get API key CLI MCP