Platform target

Netlify

Netlify can deploy Nift's normal public/ tree, so the target keeps Nift's standard output layout and adds the project-level build configuration Netlify understands.

nift init --target=netlify

What Nift creates

[build]
  command = "nift build"
  publish = "public"

netlify.toml is user-owned after initialization. Netlify's file-based configuration overrides conflicting UI build settings, so keep it as the source of truth if you adopt it.

Build environment

The generated command assumes nift is available on the Netlify build image. Choose and document the installation method for your project rather than having Nift silently inject one.

Functions and edge logic

Netlify Functions live outside the publish directory (the default functions directory is netlify/functions), while Edge Functions default to netlify/edge-functions. They can sit beside a Nift site without changing the template/build model.

Routing and headers

Netlify supports redirects, rewrites/proxies and custom headers through its static routing/configuration mechanisms. These can route requests to static files or serverless functions while Nift continues generating ordinary files.

Official references: file-based configuration, build configuration, routing, and Edge Functions.