Skip to main content

Template documentation

Public documentation for the Next.js template: setup, accounts, workspaces, API access, application runtime, and developer guidance.

SectionGeneral / Introduction
PurposePublic template documentation
UpdatedJul 6, 2026
AuthorTemplate Maintainers
Versionv1.2.0
Reading time3 min

Template documentation

This documentation explains what the Next.js application template already provides and how to use it when creating a service. It covers setup, account management, organization-backed workspaces, API keys, localization, runtime defaults, quality workflow, and release history.

Start here

General

First steps and shared terminology for template adopters.

Quick start

Create a project from the template, configure the required environment, run migrations, and verify the first local launch.

Glossary

Terms used across account, workspace, API, documentation, and development pages.

Account

Personal settings, provider connections, sessions, invitations, and deletion.

Account settings

Understand the user's global settings area and how it differs from workspace settings.

Profile and connections

Update the display name and manage configured OAuth provider connections.

Sessions and security

Review active sessions and revoke access without exposing raw session tokens.

Workspace

Organization-backed collaboration, members, teams, invitations, and settings.

Workspace

Learn how the template maps user-facing workspaces to Better Auth Organizations.

Create and switch workspaces

Create workspaces, open workspace URLs, switch context, and understand deletion boundaries.

Workspace settings

Review the settings sections for workspace details, users, invitations, teams, roles, and API keys.

Invitations

Create invitations, copy links, accept or reject decisions, and target teams.

API and integrations

Machine access with API keys and starter read-only API routes.

API access

Understand personal and workspace API keys and how /api/v1 authenticates requests.

Manage API keys

Create, edit, expire, rate-limit, and delete personal or workspace-owned keys.

API v1 reference

Review starter routes, response envelopes, principal rules, and common errors.

Application

Application shell, localization, OAuth, runtime security, caching, and settings UI.

Application shell

Review public routes, protected routes, dashboard surface, and extension points.

Localization

See how PUBLIC_DEFAULT_LOCALE controls UI messages, metadata, and documentation variants.

Runtime security

Review public base URL, image host policy, security headers, and route protection defaults.

Documentation and development

How to keep public docs, OpenSpec, E2E tests, and feature slices aligned.

How to write documentation

Write public pages with stable metadata, canonical links, and user-facing scope.

For developers

Extend a service built from the template while keeping specs, tests, and docs in sync.

OpenSpec, E2E, and docs

Use the cross-surface workflow when visible behavior changes.

History

Published releases and weekly user-visible change summaries.

Releases

Published template releases and the current release note.

Weekly changes

Short weekly notes based on real repository changes.

What the template includes

  • Application foundation: Next.js App Router, React, TypeScript, Tailwind CSS v4, shadcn/ui, server actions, settings shell, and feature-sliced structure.
  • Accounts and auth: Better Auth, configured-only OAuth providers, account settings, connected accounts, sessions, local automation auth, and protected routes.
  • Workspaces: Better Auth Organization-backed workspaces, /w/:organizationKey/... routes, settings, users, roles, teams, invitations, allowed email domains, and zero-workspace onboarding.
  • API access: personal and workspace API keys, one-time secret reveal, permissions, expiration, rate limits, and starter read-only /api/v1 routes.
  • Localization: next-intl infrastructure, English and Russian messages, localized metadata, and localized documentation content with canonical URLs.
  • Quality workflow: OpenSpec requirements, Jest, Playwright E2E, shared automation helpers, public documentation updates, releases, and weekly change notes.
Documentation localization

Documentation pages can have .en.md and .ru.md variants. The route stays canonical; the documents system chooses the variant that matches the configured UI locale and shows a language marker only when fallback content is used.