3. Customize the product

Work in the new project

Use the directory you generated in step 2. Keep the mother template available for later comparisons.

Configure the product

Open app/core/product.ts. Review name, tagline, description, domain, supportEmail, features, plans, limits, retentionDays and apiEnabled. The mother template uses siteMode="template"; the generator sets siteMode="product" for the new site's product homepage.

Text, image and audio are working reference modules. Other workflows need actual UI, provider integration, input/output handling, metering, API and recovery code. A new name or description alone does not implement a business.

Set honest pricing

amount is integer USD cents: 1900 means 19 USD. Feature credits are fixed credits per task in the current reference meter. Subscription plan credits are allocated monthly, including year-paid plans. Keep signup allowance, pricing copy, provider amounts and limits consistent.

The mother template's billing page demonstrates SaaS plans. It does not sell access to this private source template. Review billing configuration before enabling a checkout.

Replace the initial product content

In your generated project, edit Markdown in content/docs/en, content/blog/en, content/features/en and content/scenarios/en. Begin with the task your customer wants to complete. Explain steps, supported inputs/outputs, limitations, charges and retention.

The mother template keeps operator content in content/ and separate end-user starting content in starter-content/. That second set seeds newly generated projects. Do not copy the template launch instructions into customer help pages.

Keep stable IDs for translations; update slug redirects when changing URLs. Use configuration placeholders such as ioy.ai and generated plan tables. Policy text remains a draft until actual business facts are reviewed. Never invent customer logos, testimonials or revenue.

Update assets and inspect the site

Give Codex the specifications in assets/manifest.json: logo 1024×1024 transparent PNG, hero 1920×1080, blog cover 1600×900, social card 1200×630. Take product screenshots from the running app. The asset builder renders supplied source assets; it does not call an image model.

npm run assets:build
npm run content:build
npm run content:check
npm run sdk:build
npm run skill:pack
npm run check

After changing content, inspect the homepage, feature pages, quickstart, mobile layout and actual outputs. Language support starts with English; add UI, email and published translations together before enabling another locale. Continue to step 4: service configuration.