Documentation previewThese docs are actively being built. Some pages may change as the framework and examples are finalized.
Skip to content

Starter Kits

Start from a real application

GoForj starter kits render real source into your App: auth surfaces, settings screens, dashboard structure, component references, and frontend patterns your team can inspect, replace, or evolve.

A frontend foundation that belongs to your App

Starter kits are not hosted templates or framework internals. The generated files live in your source tree, alongside the backend routes, controllers, auth flow, and runtime wiring that make the App useful.

Generated GoForj starter kit dashboard shell

Forms

Account flows with real states

Sign-in, registration, password reset, profile, password, and appearance screens are generated as app-owned source. Teams start from complete flows instead of blank forms.

Local Components

Reference pages that show patterns in product context

Component examples are grouped by workflow instead of presented as a flat catalog. Forms, navigation, overlays, and data surfaces are shown inside the generated App so teams can lift patterns into real screens.

Starter kit local component reference overview

Workflow Patterns

Dialogs, commands, and layouts that feel like part of the application

The starter kit includes product-shaped overlay and navigation patterns so teams can start from realistic flows instead of isolated component demos.

App-owned by default

Use the kit, then make it yours

Starter kits provide a strong first shape. After generation, the code is yours: edit it, remove it, replace it, or evolve it into the product your App needs.

Read how starter kits are generated