Section
The layers of a web platform
Hosting
Chosen for your load and budget, configured as code where practical, with backups tested by restoring them.
Application
Server code with clear modules, automated tests and logging that helps rather than floods.
Content
A content model designed around your information, editable by your team.
Interface
Semantic, accessible HTML and CSS, progressively enhanced with script.
Specification
Deployment standard
| Environments | Development, staging and production, kept consistent. |
|---|---|
| Pipeline | Every change built and tested automatically; production deploys are repeatable. |
| Rollback | A documented way to return to the previous release quickly. |
| Performance | A page weight and loading budget agreed at the start and checked on every release. |
| Accessibility | WCAG 2.2 AA as the target, verified by tools and manual testing. |
Note
When simple is stronger
Not every website needs a database. Many company sites are best served as static files: fast, secure, cheap to host and hard to break. We will recommend this when it fits, and say so plainly when it does not.
