No Description

windhamdavid afe2d41c58 Re-export 2026-06-04 17:05 EDT		21 hours ago
README.md	597dfca356 Re-export 2026-06-04 12:13 EDT	1 day ago
footer.html	afe2d41c58 Re-export 2026-06-04 17:05 EDT	21 hours ago
header.html	afe2d41c58 Re-export 2026-06-04 17:05 EDT	21 hours ago
subdomain-shell.css	afe2d41c58 Re-export 2026-06-04 17:05 EDT	21 hours ago

SRH Static Shell Bundle

A standalone HTML + CSS bundle that lets subdomains and partner integrations render the same header + footer chrome as www.selfregional.org without depending on the WordPress runtime.

Primary consumer: the Epic MyChart prelogin shell for mychart.selfregional.org and providers.selfregional.org. Anyone else who needs the SRH brand chrome on a non-WordPress page can use these files the same way.

Files

File	What it is
`header.html`	Rendered `<header>` markup — logo, top nav, mobile drawer trigger. Drop into the `<body>` at the top of the page.
`footer.html`	Rendered `<footer>` markup — 5-column nav, social links, legal, login link. Drop at the bottom of the `<body>`.
`subdomain-shell.css`	All CSS needed to paint the header + footer. Single self-contained stylesheet — no external dependencies (fonts + logo + icons load from `https://www.selfregional.org/...` via absolute URLs already baked in).

All three files are generated from the live SRH WordPress site. They are not hand-edited — re-running the exporter against the WP source replaces them. If you need a change to the header or footer markup, request it on the WordPress side and the next export will pick it up.

Integration

The CSS file must load before the HTML fragments render. Place a single <link> in your <head>:

<link rel="stylesheet" href="path/to/subdomain-shell.css">

Then include the two HTML fragments anywhere in the body via whichever templating mechanism you already use — server-side include, fetch + innerHTML, build-time copy, etc.

Minimal page example:

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Self Regional Healthcare</title>
  <link rel="stylesheet" href="subdomain-shell.css">
</head>
<body>
  <!-- paste contents of header.html here -->

  <main>
    <!-- your application's content -->
  </main>

  <!-- paste contents of footer.html here -->
</body>
</html>

Shadow DOM hosts

If you embed the fragments inside a shadow root (the Epic prelogin shell does this — the <footer id="CustomFooter"> element has an attached open shadow tree), the CSS bundle's variable definitions ship under a :host, :root selector so the theme's CSS custom properties (brand colors, spacing scale, font sizes) inherit correctly through the shadow boundary. No additional setup needed on your end — just <link> the stylesheet inside the shadow root as you would normally.

Versioning + updates

Each file's header carries a generated banner with the export timestamp + source URL:

<!--
  SRH static shell fragment — exported 2026-06-04 12:18 EDT
  Source: https://srh.stu/  ·  Re-export: _claude/_static-export/export.py
  Asset URLs rewritten to absolute https://www.selfregional.org
-->

Updates land here whenever the WordPress source markup or CSS changes — typically: logo swap, nav restructure, footer column edit, theme color tweak. Cadence is low (weeks to months between exports under normal operation; multiple per day during active development sprints).

Pull the latest before each deploy of your consuming application. The repo's commit history captures every bundle revision in case you need to pin to a specific snapshot.

Asset URLs

All href, src, and url(...) references in the bundle resolve against https://www.selfregional.org. The SRH WordPress origin must remain reachable from end-user browsers for fonts, logos, and any external scripts to load. If www.selfregional.org is ever blocked from a consuming network, the chrome will still structurally render but assets (logo, fonts, FontAwesome icons) will fail.

Constraints + gotchas

No JavaScript in the bundle — the live SRH site uses auto-hide-nav.js to scroll-hide the header and to dynamically measure --header-height. The static bundle ships a fixed --header-height: 80px (60px on mobile) fallback instead. If your page content sits behind the fixed header, override --header-height on the host element to whatever works for your layout.
Nav menu changes are baked in. If WordPress's Appearance → Menus is edited, the change reaches this bundle only after the next export.
Login link in the footer points to wp-login on the main SRH site. If your consuming app has its own auth flow, hide that link with display: none in your own CSS rather than editing footer.html directly — keeps future exports clean.

Contact

Maintained by David Windham. Open issues here or contact via the main SRH repo if you need a bundle update or have integration questions.

README.md