Customization and upgrades
Adapt the centralized product configuration and maintain a reviewable baseline for future migrations.
Configure your productLink to section
config/product.ts groups your product settings. Keep credentials in the
server environment.
Identity and presentation
brand,linksandnavigationcontrol names, documentation destinations and menu structure.moduleschanges presentation; server authorization remains independent.emailcontrols accent, contact and Reply-To identity. The sender still needs verification.
Plans and capacity
billing.trialDaysconfigures the checkout trial.workspaces.limitscaps workspace creation per account.entitlementssets projects, members and invitations per workspace.
Quotas and billing ownership
Quotas default to null, meaning uncapped. Use non-negative integers when
your offer needs limits, then test the boundary and upgrade path. Billing
remains personal; an organization-owned subscription needs a separate design.
Customize provides palette, typography, geometry, interface scale and sidebar
controls in the browser. Language and time zone are account preferences. Review
changes in both themes, French/English, narrow layouts and reduced motion. The
shipped docs/customization.md explains logo, icon and email entry points.
Configure appearanceLink to section
Use the Theme Builder for the shared palettes, fonts and radius scale. Open Dashboard preview to choose density, interface scale, sidebar, content width, canvas and motion.
- Choose your colors and appearance settings.
- Select Download Starter Pro config, then replace
config/appearance.ts. - Restart the app. In a browser with saved preferences, use Customize → Reset.
Saved browser choices take precedence over product defaults. The selected preview
mode becomes the initial light/dark mode; set mode: "system" in the config to
follow the device. Named presets use the bundled shared tokens. Custom colors
include both semantic color maps and appear as Custom in Customize.
This export requires Starter Pro source with lib/appearance-contract.ts. For an older
project, upgrade first or use the CSS exports.
The buyer ZIP includes the configuration contract, color snapshots and local font assets. It does not require a private workspace package or a Theme Builder server.
Work with a coding assistantLink to section
Start with the included instructions
In the extracted project, read AGENTS.md, then docs/ai/README.md and
docs/ai/conventions.md. CLAUDE.md points to the same shared instructions.
These files describe the installed source, its server boundaries and its
validation commands. Use your own coding assistant.
A protected page
- Recipe: docs/ai/add-page.md
A business resource
- Recipe: docs/ai/add-resource.md
A new permission
- Recipe: docs/ai/add-permission.md
Adopt the recipes explicitly in your own project. The buyer-ZIP validator applies their code to a disposable extracted copy, compiles it and exercises allowed, denied, revoked and cross-workspace cases. Keep schema and billing decisions explicit when your own adaptation needs them.
For a complete workflow, choose a business recipe: client tracking, an internal support queue or an internal review checklist. The guides map existing projects, tasks and comments to each workflow, then separate presentation changes from domain fields and access rules to design.
Keep an upgrade baselineLink to section
Commit the original delivery into a private repository before customization.
Retain PYCOLORS_RELEASE.json, the lockfile, patches, changelog, licence and order
terms. Compare a newly available delivery against that baseline and merge your
adaptations through review. Future-version access follows the purchased offer.
Rehearse migrationsLink to section
Review the incoming releaseLink to section
Read the changelog, pending SQL and environment changes before installing.
Prepare restricted stagingLink to section
Restore a recoverable backup into a restricted staging environment.
Install and inspect migration statusLink to section
pnpm install --frozen-lockfilepnpm exec prisma migrate statusApply reviewed migrationsLink to section
pnpm exec prisma migrate deployKeep migrations already applied to retained data immutable. The project-work migration adds task/comment tables and preserves existing projects.
Validate the applicationLink to section
Run diagnostics, tests, a production build and the affected user journeys. Session-registry upgrades can require users to sign in again.
Verify providers before rolloutLink to section
Check provider integration in a sandbox before deploying the reviewed result.
Plan recovery before deployment
Retain the previous application artifact and check schema/session compatibility before rollback. There is no automatic destructive down-migration. A database restore can lose writes after the chosen recovery point; use your incident procedure.