Getting started
From download to running, adding modules, settings, connecting a real backend, design and updating - everything you need on day one.
Buy the edition you need with PayPal on the pricing page. It's a one-time purchase, not a subscription.
My account in the header → My products. The React, Vue and Next.js zips contain the edition folder and the shared mock backend (initfn-mock) side by side.
initfn-react-1.0.0/
initfn-react/ # React edition
initfn-mock/ # mock backend (found at ../initfn-mock - keep both side by side)Node.js 24 (see .nvmrc in each edition) and npm. Not needed for Vanilla.
Start the mock backend, then the app. Sign in with admin / 1234.
cd initfn-mock && npm i && cd ..
cd initfn-react && npm i # initfn-vue for Vue
npm run mock # mock backend http://localhost:4000
npm run dev # React :4001 · Vue :4003 · docs at /docStart with the Next server alone (monolith) or connect it to the mock backend.
cd initfn-nextjs && npm i
npm run mock # when using the mock backend
npm run dev # http://localhost:4002 · docs at /docNo build step. Open the HTML files in _guide in a browser for usage and example source, then link the css, js and font folders from your pages.
React, Vue and Next.js editions add or remove any of 50 modules with one command - screens, APIs and menus come and go together.
npm run preset # list modules
npm run preset add social-login mfa # add
npm run preset remove mfa # removeThe React, Vue and Next.js editions split settings into three files. .env holds values shared by dev and production (nothing secret, like the site name), .env.development is for development only and .env.production for production only. None of them go into git, and values that only apply to your machine go in .env.local.
.env # shared, not secret - site name, public IDs
.env.development # dev only - local backend URL, sandbox keys
.env.production # production only - live URL, live keys, analytics ID
.env.local # your machine only (overrides the others)When you add a module, the settings keys it needs are added to the end of the right file with a comment explaining each, and you get a list of the keys still to fill in. Values you already have are never touched, and removing a module doesn't delete them.
npm run preset add paypal
# -> adds PAYPAL_* keys to .env.development
# and .env.production, then lists keys to fillThe backend address is one row in core/config/apiConfig.js and one line in .env.development (.env.production in production). Screen code stays the same.
# .env.development (production: .env.production)
BACKEND_API_URL=http://your-backend:8080initfn-mock/openapi.yaml describes the API the frontend expects. Give it to your backend developers - a backend that responds this way connects without code changes.
Styles come in three layers. Values like colors, fonts, radius and shadows go in initfn-token.css, the look of small UI like buttons, inputs, cards and blocks in initfn-base.css, and larger designs like pages and sections in initfn-global.css. To change just the brand color, edit only --color-brand-* at the bottom of the token file.
src/core/style/ # Vanilla: css/ · font/ · image/
css/initfn-token.css # values - colors, fonts, radius, shadows
css/initfn-base.css # small UI, components, blocks
css/initfn-global.css # pages and sections
font/ image/Give it a mockup or the feel you want, and ask it to read the design skill included in your edition and apply it. The skill says which file to change for each kind of request, so the AI edits these three files and leaves screen code alone.
.claude/skills/ssr-design/ # Next.js
.claude/skills/csr-design/ # React
.claude/skills/vue-design/ # Vue
.claude/skills/vanilla-design/ # VanillaCSS is written one rule per line (only the token file uses line breaks), and VS Code tidies it automatically when you save. Fonts load only the Pretendard pieces a screen needs, so first-screen fonts are about 1MB. In the React, Vue and Next.js editions, the shared Image component lazy-loads images and serves them light as avif/webp.
npm run format # tidy CSS - one rule per line
node scripts/format-css.mjs # VanillaIn the React, Vue and Next.js editions, copy the .preset folder from the new zip over your project's .preset, then run update. In the list, ⬆ marks installed modules with a new version and 🆕 marks new modules. Files you changed are never overwritten - the new version is placed next to them as .preset-new, so compare, merge, then delete it.
# 1. copy .preset from the new zip over your project's .preset
npm run preset # 2. list - ⬆ update available · 🆕 new module
npm run preset update # 3. update installed modules
npm run preset add <name> # 4. add a new module
npm run lint && npm test && npm run buildWhich modules you added, and at which version, is recorded in preset.lock.json at the project root. It lives outside the .preset folder so the record survives overwriting that folder - commit it to git as well.
To also get improvements to base code like core and shared, start a git repository from the zip and keep the untouched original on an initfn branch. Do your own work on main.
git init && git add . && git commit -m "initfn 1.0.0"
git branch initfn # untouched originalDownload the new zip, overwrite the initfn branch, merge it into main, then run npm run preset update to sync your installed modules. Only places you changed yourself show up as conflicts. See the release notes for what changed.
git switch initfn
# unzip the new version over it (keep node_modules and your .env files)
git add -A && git commit -m "initfn 1.1.0"
git switch main && git merge initfn
npm run preset update # sync installed modulesEvery edition has the same command names.
npm run lint && npm test # rules and unit tests
npm run build # production build
npm run test:e2e # browser E2EDeployment is covered in the in-app developer guide (/doc). When you deploy or deliver an End Product, include THIRD_PARTY_NOTICES.md (open-source notices) from the edition.
The full, detailed guide comes inside the project archive. This page only covers what you need on day one. Everything else - installation, settings, components, modules and deployment - is in the downloaded archive: the built-in guide site (7 languages), the README and the docs for AI coding tools (AGENTS.md).
Check the FAQ and license, or tell us at numerxlab@gmail.com.