44bd1446f5
- docs/backend: admin controllers, forms, lists and filters, relation manager, users and permissions, settings, partials and widgets, admin SPA - docs/services: storage, outbound HTTP, realtime, Web Push, search, parity testing and the Frontend and AJAX (not provided) page - Examples for cabana (with testdata/docs YAML), fetchguard, lighthouse and its centrifugo driver, flare, beachcomber and typesense, tide; lighthouse and beachcomber TestDocs* regions run on their Postgres harnesses - concept map rows link their guide pages and the not-provided rows the Frontend and AJAX page; index lists Backend, Database and Services - TestDocsRequiredPages asserts the D-08 section order
1.6 KiB
1.6 KiB
title, description, section, order
| title | description | section | order |
|---|---|---|---|
| SummerCMS documentation | SummerCMS is a content management framework for Go, inspired by WinterCMS. | index | 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 to set up the toolchain and the summer CLI. If you know WinterCMS, read Coming from WinterCMS for a map of its concepts to SummerCMS. The API reference section has one page per framework module.
Where to start
- Setup: what SummerCMS is, installation, configuration and the move from WinterCMS.
- Architecture: the single binary, Go modules, the application lifecycle and the request lifecycle.
- Plugins: registering a plugin, scheduling, extending other plugins and testing.
- Backend: admin controllers, forms, lists, relations, users, settings and the admin SPA.
- Database: models, migrations, queries, relations, casts, attachments and transactions.
- Services: configuration, events, routing, authentication, mail, jobs, realtime, search and the other services, plus what SummerCMS does not provide for the frontend.
- Console: the
summertool, the application binary's commands and writing your own.