Discipline — Web development
Web development
Websites and web applications with measured performance, accessible structure and documentation that lets anyone maintain them.
Page weight budget, accessibility target and hosting arrangement written into the specification for every build.
Informational sites
A focused set of pages, static or lightly managed, with low hosting cost and minimal attack surface.
Managed content
Sites with editors, workflows and search on a content system selected for the people who will use it.
Web applications
Authenticated tools, portals and dashboards with databases, roles and audited integrations.
Baseline specification
- Markup
- Semantic HTML, one heading hierarchy per page, labelled controls.
- Layout
- Responsive and checked at phone, tablet and desktop widths.
- Performance
- Page weight budget agreed and checked before release.
- Forms
- Validation that preserves input and explains failures.
- Security
- HTTPS, security headers, updated dependencies, secrets outside the code.
- Third parties
- Every external script listed, justified and approved by you.
- Search
- Unique titles and descriptions, sitemap and robots file.
Note
Fewer moving parts, fewer failures
We prefer simple, well-understood technology where it does the job. A static website cannot be hacked through a plugin it does not have. A web application with three well-chosen dependencies is easier to keep secure than one with thirty. We will explain the trade-offs when a more complex stack is justified.