How EdgePress builds your website

How EdgePress builds your website

Markdown articles and page blocks become a static website. Browser features run locally; optional services load after consent.

Where content belongs
PathPurpose
content/posts/<article>/en.mdArticle front matter and Markdown body
content/pages/<page>/en.jsonPage JSON metadata with ordered layout blocks
content/assets/Published pictures and other content assets
themes/<theme>/HTML layout and theme styles
config.ymlNavigation, theme and optional service disclosures

Use Node.js 22.12 or later. The build generates dist/. Cloudflare, Vercel, Netlify, EdgeOne Pages and ESA Pages can host these static files. Hashed CSS and JavaScript are cached for one year; HTML revalidates.

npm ci
npm run dev
npm run build

Register each service by name under plugins.consent.services. Before consent, its resources are not loaded. When consent is granted, visible embeds load on demand. Authentication, storage and other backend work belong to the independent service, with platform adapters under backend/<platform>.