Technology and infrastructure
Websites built to be operated, not just launched
Operloom designs and builds websites as part of the operating model: connected to the CRM, measurable end to end, and editable by the people who own the content.
01Business problems
The website is usually a symptom
Most website problems trace back to decisions made elsewhere: no content owner, no measurement plan, no integration contract with the CRM.
- Editors cannot publish without a developer
- Forms submit but nothing reaches an owner
- Page speed degrades quietly after launch
- Tracking breaks and nobody notices for a quarter
- Accessibility is discovered during a procurement review
02Implementation scope
What a build actually covers
Scope is agreed against the journeys the site has to support, then sequenced so each release can be verified on its own.
- 01Information architecture and URL strategy
- 02Design system and component library
- 03Templates, content model and editor experience
- 04Forms, consent capture and CRM integration
- 05Performance, accessibility and technical search
- 06Hosting, deployment and rollback
03Platforms
Chosen for who has to maintain it
The right platform depends on the editing team, the integration surface and the tolerance for ongoing maintenance, not on preference.
- WordPress
- Drupal
- Webflow
- Shopify
- Astro
- Next.js
- Headless CMS
04Migration
Move without losing what ranks
A migration plan protects URLs, redirects, structured data and measurement continuity before a single page is switched over.
- 01Full URL inventory and redirect map
- 02Content audit, with retirement decisions recorded
- 03Structured data and metadata carried across
- 04Analytics and tag continuity
- 05Staged cutover with a rollback path
05Performance and accessibility
Budgets, not aspirations
Performance and accessibility targets are set before the build and checked on every release, because both degrade the moment they stop being measured.
- Core Web Vitals budgets per template
- Image, font and script loading strategy
- WCAG 2.2 AA as the build standard
- Keyboard and screen reader testing
- Automated checks in the deployment pipeline
06Content operations
Leave the team able to publish
The content model is designed around how the team actually works, and the editor experience is part of the deliverable.
- 01Reusable blocks with editorial guidance
- 02Preview and publishing workflow
- 03Roles, permissions and review steps
- 04Editor documentation and training
- 05A backlog of the things worth improving next
Common questions
Question: Can you work with an existing website rather than rebuilding it?
Often, yes. An audit of performance, accessibility, content model and integration usually shows whether targeted work will hold, or whether the underlying structure is the constraint.
Question: Who owns the site after launch?
You do. The code, the hosting account, the domain and the documentation are yours, and the handover includes the training needed to run them.
Related capability
Where this connects
Next step
Build a systemyour team can actually run
Start with the process as it works today, the platforms already in play and the outcome the organisation needs. We will tell you what we would change and in what order.