How are the websites built?

Rendered on the server, so every page is complete HTML before any script runs. genyra.com is built the same way and measured in Lighthouse before each release.

Will the site load third-party scripts?

No analytics, advertising or third-party scripts unless the organisation asks for a named one, and then it is listed in the design.

Do you host what you build?

Yes. Hosting, deployment and backup are designed with the site. We can operate it or hand it over with the records.

SOFTWARE / WEB DEVELOPMENT

Complete before the first script.

Websites and web platforms that are rendered on the server, readable without scripts, measured for performance and accessibility, and operated with the hosting they were designed for.

Discuss the work

The controls activate with JavaScript. The illustrative rules, record and scope remain readable below. No information is sent or saved.

Interactive engineering study

In memory · local only

Document reviewWorkspace / 014

Reporting workspace

Illustrative brief · DOC-014

Draft

Current requirement · offline reporting

The reporting view must remain usable offline.

Choose the sensitivity and assign a reviewer.

01Draft02Reviewer03Queued

Review policyRules / 01

Reporting workspace / review decision

Assign a reviewer first.

Current requirement · offline reporting

The reporting view must remain usable offline.

Sensitivity InternalReviewer Not assigned

01 / PermissionBlocked
02 / Queue if allowedStandard review
03 / ConsequenceNo event created

No review event can be created until a reviewer is assigned.

Current outcomeReviewer required

Inspect logic

if (!reviewerAssigned)
  return "needs_reviewer";

return sensitivity === "Restricted"
  ? "controlled_review"
  : "standard_review";

Record & eventsData / local

Reporting workspace / current recordDraft

No submission yet.

Current requirement · offline reporting

The reporting view must remain usable offline.

Document: Reporting workspace · DOC-014
Review queue: Not queued
Latest event: None yet

No event has been created for this brief.

Submission events0

No submission event yet. Use the interface to create one.

Inspect record

{
  "id": "DOC-014",
  "subject": "Reporting workspace",
  "requirement": "The reporting view must remain usable offline.",
  "sensitivity": "Internal",
  "reviewerAssigned": false,
  "status": "draft",
  "queue": null,
  "lastEventId": null
}

01Inside the work

Websites and web platforms, rendered on the server.

Every page is complete HTML when it leaves the server: the content, the navigation, the forms and their results. A browser with scripts blocked, a search engine, a screen reader and an AI assistant all receive the same document. Scripts arrive afterwards and add motion and interaction; they never carry the content.

The same approach serves a corporate site, a client portal with sign-in and a web platform that records and reviews work. The difference is what the server holds, not how the page is built.

02Scope / considerations

Performance and accessibility are engineering targets.

Load time, layout stability, contrast and keyboard operation are stated as targets before the design starts and measured before each release. Fonts and images are served from the site itself, sized for the device that asks, and nothing shifts after the first paint.

Accessibility is checked the same way: contrast ratios, heading order, labelled controls and focus that is visible, verified in the lab and kept in the build.

Server-rendered content with no client-side dependency
Images and fonts served by the site, sized per device
Contrast, heading order and focus verified
Measured per release, not once

One request to a Genyra-built page · how this site is delivered

browserVisitor

GET /software/web-development
host: genyra.com
accept: text/html
sec-fetch-dest: document

Status: Request sent · awaiting document
Scripts: none requested yet

Added after the content

entrance choreography · transform only, text never hidden
stepping and tracing in the figures
motion preference honoured; off by default when the device asks

still readable if this step never happens

Lighthouse scores · mobile lab profile

Performance: 99
Accessibility: 100
Best practices: 100
SEO: 100

genyra.com · Lighthouse 13.6 · mobile lab · 31 Oct 2026

edge → originGenyra-built

200 text/html; charset=utf-8
x-content-type-options: nosniff
x-frame-options: DENY
referrer-policy: strict-origin-when-cross-origin
content-security-policy: frame-ancestors 'none'; object-src 'none'; base-uri 'self'
permissions-policy: camera=(), microphone=(), geolocation=()

01<main id="main" class="interior-page">
02  <p class="eyebrow">SOFTWARE / WEB DEVELOPMENT</p>
03  <h1>Complete before the first script.</h1>
04  <p class="page-lede">Websites and web platforms …</p>
05  <nav aria-label="On this page">
06    <a href="#security">03 Security built into the request.</a>
07  </nav>
08  <section id="security">
09    <h2>Security built into the request.</h2>
10    <p>The server checks the origin of every form …</p>
11  </section>
12</main>
13<!-- loads after the content; the page above is already complete -->
14<script type="module" src="/_app/immutable/entry/start.js"></script>

Complete at the server, enhanced afterwards, measured before release. Scores are a local lab measurement, not a guarantee.

03Inside the work

Security built into the request.

The server checks the origin of every form submission before it is accepted. Responses carry the security headers that prevent framing, sniffing and unwanted referrers. The only third-party script is Google Analytics on the public pages; advertising and social scripts are absent, and the account cookie is set only when someone signs in.

Private areas are rendered server-side behind a session, with staff actions recorded in an audit trail.

04Inside the work

Forms and enquiries that record and acknowledge.

An enquiry is validated on the server, recorded with a reference and acknowledged on the page with that reference. A repeated submission with the same reference returns the same record rather than a duplicate. The record and its history stay in the organisation’s own database.

05Inside the work

Hosting and operation designed with the site.

Where the site runs, how it is built and promoted, what is backed up and who may deploy are decided with the design, not after it. The release is reproducible from source, the server is configured as a record, and the operating duties are named in writing.

06MEASURED

This site is the demonstration.

genyra.com is built the way this page describes and is measured the same way. In Lighthouse 13.6 mobile lab runs on 31 October 2026, every measured page scored 100 for accessibility, best practices and SEO. Performance scored 99–100 on all but one page; the company page, which loads its opening image eagerly, scored 92. No contrast failures were reported, and every page is complete with JavaScript blocked.

These are local laboratory measurements of this site on the day stated. They describe how it is engineered, not a guarantee of any score on any device or network.

Before an enquiry

Questions we are asked.

Short answers in the same terms as the page. Anything specific to your systems is agreed by enquiry.

How are the websites built?: Rendered on the server, so every page is complete HTML before any script runs. genyra.com is built the same way and measured in Lighthouse before each release.
Will the site load third-party scripts?: No analytics, advertising or third-party scripts unless the organisation asks for a named one, and then it is listed in the design.
Do you host what you build?: Yes. Hosting, deployment and backup are designed with the site. We can operate it or hand it over with the records.

A CLEARER NEXT STEP

Discuss a web project

From an unanswered question
to an engineered possibility.

Discuss a web project