Infrastructure · HELPERG
helperg.com completes its move to a generated static architecture
The site is now built from a single source of truth and published as static files. Page URLs, canonical addresses and analytics behaviour were preserved unchanged.
helperg.com has completed a migration from hand-maintained HTML pages to a generated static architecture. The work was staged over several phases and is now complete for every page in scope.
What changed
Pages are now generated from shared components and per-page content rather than maintained as independent HTML files. The published result remains static files — there is no server-side rendering and no client-side application framework.
What deliberately did not change
The migration’s constraint was that nothing observable should move:
- URLs are unchanged. No page was renamed, redirected or restructured.
- Canonical addresses are unchanged, including the site’s mixed convention of
root
.htmlpages and directory-style hubs. - Analytics coverage is unchanged page by page. Pages that carried no analytics before still carry none, and consent behaviour is unchanged.
- The sitemap is unchanged in membership and ordering.
What a reader can check
Two consequences are directly observable on any page of this site: it serves two JavaScript files — a consent script and a small navigation script — and it requests no application-framework runtime. There is no React, Vue, Svelte or Solid bundle, and no hydration step.
Why it was done
Maintaining a growing site as independent HTML files means every shared change — a navigation item, a footer link, a consent adjustment — has to be repeated on every page, and drifts when it is not. Generating from a single definition removes that class of inconsistency without changing what visitors receive.
Status
Complete for all in-scope pages. Two internal preview routes are deliberately excluded from the site architecture and are unchanged.