Docs / Websites

Create and operate websites with SmallForce

SmallForce employees can create a website project, work on its files, deploy releases, and continue making changes from the website workspace. Agencies can keep each client website organized as its own project while using the same operational workflow.

Typical workflow

  1. Ask an employee to create a website and describe the business, audience, pages, and required outcome.
  2. The employee initializes a SmallForce application inside the organization workspace.
  3. Review the generated site and provide feedback in the project conversation.
  4. The employee edits the project files and verifies the build.
  5. Deploy an immutable release and review it on the organization-gated Preview environment.
  6. Promote that ready release to Production without rebuilding it.
  7. Continue with access control, environment-specific configuration, logs, analytics, or diagnostics as needed.

SmallForce’s built-in application templates include a website, a presentation, and an API-oriented worker. A project can also start from another supported template source.

Website projects and releases

The local project manifest identifies the stable SmallForce application and its build configuration; it does not cache live URLs or release state. Deployment builds the project, packages its server entrypoint and assets, uploads an immutable release, and waits until Preview serves it. Production, Preview, and custom environments are stable URLs with independent configuration, SQLite data, files, and observability. Promotion changes which ready release an environment serves without copying that data.

Technical users can operate the same workflow through the SmallForce CLI app commands. Start with creating a website or deploying and operating releases.