For Developers¶
Summary¶
Start here for SkyCMS developer architecture, API, lifecycle, and implementation guidance.
SkyCMS supports a code-first development model without sacrificing editor usability. Developers can implement and maintain websites with familiar architecture and tooling, while content teams continue routine updates through visual editing.
Role overview¶
SkyCMS content roles work together like this:
- Editors run day-to-day content workflows.
- Site builders control presentation structure and design systems.
- Developers own application behavior, extensibility, and operations.
In this section, a developer is the person responsible for building and maintaining SkyCMS internals, integrations, and platform reliability.
Developers typically:
- Implement and maintain features, APIs, and middleware.
- Define and evolve content lifecycle behavior.
- Build integrations for storage, auth, and external services.
- Maintain performance, observability, and deployment quality.
- Add tests and uphold architecture and tenant isolation constraints.
Developer experience philosophy¶
SkyCMS is designed to remove unnecessary constraints on implementation style. You can work through templates, APIs, infrastructure, and IDE-centric workflows instead of being locked into a rigid CMS authoring model.
When you want to interact with CMS content and structure from inside your IDE, use the SkyCMS VS Code Extension to work with SkyCMS resources as code.
For the complete permission matrix and cross-role responsibilities, see Roles and permissions (RBAC).
Start here¶
If you are new to SkyCMS development, start with these five pages:
- Developer guide overview
- Architecture overview
- Core platform architecture
- API docs overview
- Website launch workflow
Then go deeper by task¶
Architecture and platform¶
- Architecture diagram catalog
- Architecture executive summary
- Architecture decision matrix
- Architecture mode selection worksheet
- Architecture route inventory templates
- Static architecture profile
- Dynamic architecture profile
- Hybrid architecture profile
- Architecture review checklist
- Architecture change log
- Middleware pipeline
- Multi-tenancy deep dive
Implementation and delivery¶
- Layouts
- Templates
- Layouts, templates, and articles
- Article lifecycle
- Publisher rendering flow diagrams
- Roles and permissions (RBAC)
- Configuration overview
- Creating editable areas
Documentation standards (internal)¶
- Documentation standards stack v1
- Documentation visual style standard (DVSS)
- Documentation metadata schema v1
- Documentation templates
- Documentation PR checklist
- Documentation adoption priority plan
- Documentation rollout plan
- Documentation standards gap review and upgrade plan (2026-04)
Verification¶
You are in the right developer workflow when you can identify the correct architecture and API references for your task, apply the related implementation guide, and validate changes against platform constraints.