a896f3ff81
- setup: introduction, installation rewritten from install to serve, configuration with the keys an application sets - console: introduction, setup and maintenance, scaffolding, writing commands, utilities; every command name is checker-verified - bonfire ExampleCatalog shows arguments, bare and repeatable flags - index links the section introductions; TestDocsRequiredPages lists the seven new pages
19 lines
1.2 KiB
Markdown
19 lines
1.2 KiB
Markdown
---
|
|
title: SummerCMS documentation
|
|
description: SummerCMS is a content management framework for Go, inspired by WinterCMS.
|
|
section: index
|
|
order: 0
|
|
---
|
|
# SummerCMS documentation
|
|
|
|
SummerCMS keeps what makes WinterCMS productive (plugins that extend each other, YAML-driven admin forms and lists, console scaffolding) and compiles an application into a single Go binary. The framework modules, the application's plugins, the embedded admin SPA and the console commands all ship as one executable.
|
|
|
|
Start with [Installation](setup/installation.md) to set up the toolchain and the `summer` CLI. If you know WinterCMS, read [Coming from WinterCMS](setup/coming-from-wintercms.md) for a map of its concepts to SummerCMS. The API reference section has one page per framework module.
|
|
|
|
## Where to start
|
|
|
|
- [Setup](setup/introduction.md): what SummerCMS is, installation, configuration and the move from WinterCMS.
|
|
- [Architecture](architecture/introduction.md): the single binary, Go modules, the application lifecycle and the request lifecycle.
|
|
- [Plugins](plugins/registration.md): registering a plugin, scheduling, extending other plugins and testing.
|
|
- [Console](console/introduction.md): the `summer` tool, the application binary's commands and writing your own.
|