BusinessOS Docs

Builder workflow (project owners)

This guide describes how builders use the platform day-to-day.

1) Create a project

• Create a project (slug becomes its subdomain on the project-site host).
• Project status:
  • draft: not publicly available
  • live: available to end-users
  • archived: disabled

2) Enable modules for a project

Modules are enabled per project from:

• Builder Marketplace (/modules → open module details → enable per project)
• Inside a project, via Project Modules navigation (preferred operational flow)

Enabling a module attaches its capabilities to that project:

• Backoffice admin pages + APIs
• Optional public site pages + end-user APIs

3) Select the core module

Each project must have one core module.

Why:

• Landing page (/) uses core module template
• Site shell can adapt layout rules based on the core module
• Authenticated end-user area is template-defined (for example /portal, /courses, /products)

Storage:

• project_module_installations.config.isCoreModule = true

4) Publish content

Content/publishing is module-owned:

• Courses: publish course records; lessons become available to end-users
• Products: publish products; assets become downloadable for entitled users

4.1) Landing customization (template-aware)

Project owners manage public landing content from Project settings → Landing Page.

• Generic fields: headline, subheadline, CTA.
• Template-specific fields: per-section visibility and copy controls defined by the active template.
• Example (AI SaaS): hero badge text + visibility and hero stats visibility are configurable directly in landing settings.

5) End-user auth + authenticated area

End-user login is provided by end-user-auth.
Authenticated post-login area is provided by template + module site routes.

• End-user session cookie: project_session
• End-user pages must resolve project context via resolveProjectContext() (handles cache misses)

6) Legacy dashboard data contract (deprecated)

/dashboard is now a compatibility redirect.
Do not build new module features around dashboard aggregation.

If legacy projects still use dashboard section descriptors, treat them as transitional only.