Step 01
1. Frame the request
The route, section and authorised files are defined before any change is made.
Route and scopeStudio Hermes
Describe the target, generate a visual, approve it, then let Hermes integrate it in the right place.
Generated for the page, then selected before implementation.
A governed workflow
Every step has a clear input, an identifiable validation and a verifiable output.
Step 01
The route, section and authorised files are defined before any change is made.
Route and scopeStep 02
The visual supports the story without turning the content into a single image.
Visual variantsStep 03
The selected variant becomes the single reference used for integration.
Selected referenceStep 04
Headings, steps, cards and CTAs remain native HTML/CSS, accessible and translatable.
Native DOM, CSS and JSStep 05
Build, routes, languages, responsive behaviour, keyboard, console and network are checked before handoff.
Quality evidenceThe right level of intervention
Studio Hermes adapts its scope to the intent without silently expanding the reach of the change.
Target 01
Adjust a block that is already present while preserving the rest of the page’s structure, content and interactions.
Focused interventionTarget 02
Add a new sequence to the existing story and connect it naturally to the surrounding sections.
Controlled extensionTarget 03
This exampleCompose a complete route with its hero, content, metadata, languages and quality checks.
End-to-end productionVerifiable delivery
The result remains editable, localised and testable. The visual supports the page; it never replaces the content.