A local design candidate
On 16 June, a fuller v5 website was prepared locally while the existing v4 message remained the public baseline. The work retained the publishing house’s central purpose and reused its approved images, rather than treating a redesign as permission to invent a new identity.
A separate, commented stylesheet carried the visual rules. The candidate used static HTML and CSS without a runtime Tailwind dependency. This reduced the amount of presentation logic embedded in the page and made individual style decisions easier to inspect.
Testing a page as a reader sees it
The session record describes desktop and mobile preview checks. Images loaded, the checked layouts had no horizontal overflow and the next section remained visible within the opening view. Those observations apply to the tested candidate and viewports; they are not a general performance score.
Metadata, icons and social-preview material were also part of the candidate. The useful principle was that page content, visual treatment and machine-readable information need to be reviewed together.
Scope matters in public copy
The same session declined to add a public organisational-status claim that the foundation documents did not establish. That is an editorial decision with technical consequences: templates and metadata should not multiply an unsupported assertion across a site.
V5 was a local candidate at this point. Preparation and browser checks did not make it a published release. Keeping that distinction in the version record prevented the new folder’s existence from being mistaken for a change on the public website.
Evidence for this entry
This account is grounded in project records. Internal research and operational files are not published here.
What the records support
- V5 local candidate, CSS separation, brand preservation, desktop/mobile QA and no publication.