e0640220f2
- installation: one-liner first, what the script does and its overrides, running the generated app, summer new without the script, then the examples/hello walkthrough; the obsolete known-issues callout is gone (D-18) - go modules and workspaces: what summer new writes (relative replace, framework detection order, committed relative go.work, no root go.sum); plugin:add adds a relative go.work path - console scaffolding: Creating an application with --framework, --no-plugin, --no-git, the files written, first commit and naming convention (D-01) - console introduction, llms note in site.yaml, root README quick start
31 lines
1.2 KiB
YAML
31 lines
1.2 KiB
YAML
# Documentation site configuration, read by `summer docs:build`.
|
|
# Sections are listed in sidebar order; each must have at least one page.
|
|
title: SummerCMS
|
|
description: "SummerCMS is a content management framework for Go, inspired by WinterCMS."
|
|
base_url: ""
|
|
edit_url: "https://git.golem15.com/golem15/summercms/_edit/master/{path}"
|
|
source_url: "https://git.golem15.com/golem15/summercms/src/branch/master/{path}"
|
|
llms_notes:
|
|
- "Plugins are Go modules compiled into the application binary and registered at build time; nothing is loaded at runtime."
|
|
- "The data layer supports PostgreSQL only."
|
|
- "SummerCMS is headless: it serves a JSON API and an admin SPA, with no frontend themes."
|
|
- "It targets Go 1.27."
|
|
- "A new application starts with `curl -fsSL https://summercms.io/new | bash -s -- <name>`, or with `summer new <name>` next to a framework checkout."
|
|
sections:
|
|
- name: setup
|
|
title: Setup
|
|
- name: architecture
|
|
title: Architecture
|
|
- name: plugins
|
|
title: Plugins
|
|
- name: backend
|
|
title: Backend
|
|
- name: database
|
|
title: Database
|
|
- name: services
|
|
title: Services
|
|
- name: console
|
|
title: Console
|
|
- name: api
|
|
title: API reference
|