Quick start

Stackiln is currently distributed from source while its package surface is prepared. On Windows PowerShell, use pnpm.cmd when the execution policy blocks pnpm.ps1.

• Node.js 24
• pnpm 9
• Docker Desktop or Docker Engine with Compose
• Git for cloning Stackiln and versioning the generated product

Start the local Studio from the Stackiln checkout, then open http://127.0.0.1:4173. Choose a page recipe, search the 60-block catalogue, arrange the page, and edit its content and theme before exporting.

git clone https://github.com/Stackiln/stackiln.git
cd stackiln
pnpm install --frozen-lockfile
pnpm stackiln studio ../my-product

Clone Stackiln, install its pinned dependencies, and generate into a directory beside the framework checkout. The marketing preset is the implemented starting point.

git clone https://github.com/Stackiln/stackiln.git
cd stackiln
pnpm install --frozen-lockfile
pnpm stackiln create ../my-product \
  --preset marketing \
  --name "My Product" \
  --description "A clear description"

Open http://localhost:3000. Review every environment value before deploying. The generated repository is independent and has no Stackiln runtime dependency.

cd ../my-product
cp .env.example .env.local
pnpm install --frozen-lockfile
docker compose up -d --wait db
pnpm db:migrate
pnpm dev

Add the accounts module at creation time for verified email/password sign-up, sign-in, recovery, profile, session, export, and deletion foundations. Accounts requires the email module, which Stackiln resolves automatically.

pnpm stackiln create ../my-product \
  --preset marketing \
  --module accounts \
  --name "My Product"

Inspect reports the resolved preset, modules, framework version, deployment target, and changed managed files. Doctor exits non-zero when a managed file differs from its recorded checksum.

cd ../stackiln
pnpm stackiln inspect ../my-product
pnpm stackiln doctor ../my-product