Great instincts on both counts. Let me address each.

1. The "Moon Sighted" reset button

This is exactly the right call for a sighted-moon ministry — the math should defer to the actual observation. Here's the simple architecture:

Backend side (one tiny endpoint):

• Stores a single value: last_sighting_date (e.g. 2026-04-17)
• A password-protected admin page with one big button: "Moon Sighted Tonight — Reset to Day 1"
• That button writes today's date (Jerusalem time) to the stored value

Frontend side (this page):

• On load, fetches last_sighting_date (or reads it from a JSON file the admin page writes)
• Calculates daysSinceSighting = today - last_sighting_date + 1
• Picks moon_01.png through moon_30.png based on that number
• Falls back to the synodic-month math if the fetch fails

The whole thing is maybe 80 lines of PHP/Node + a JSON file. Want me to mock up the admin button page so you can see what it would look like?

2. Bringing this page to stg-sightedmooncom-sm2026.kinsta.cloud

You've got two realistic paths. Which one depends on whether you want this to live alongside the current WordPress site or replace the homepage.

Path A — Drop-in replacement for the WP homepage (recommended for now)

Lowest risk. The current site stays exactly as-is; only the front door changes.

1. Export this page as a single self-contained HTML file (I can do this in one click — bundles all images, fonts, CSS into one file)
2. Upload that file + the assets/moon/ folder to your web host (via FTP or your host's file manager)
3. In WordPress: install a plugin like "Insert HTML Snippet" OR set the homepage to a static page that just embeds the HTML
4. The "Enter the Site" button links to the existing WP homepage at /home or wherever you move the old one

Pros: Nothing on the existing site breaks. You can A/B test by toggling. Reversible in 30 seconds. Cons: Two systems to maintain (the new homepage + the WP site behind it).

Path B — Full site rebuild around this design language

Bigger project. This becomes the visual system for the whole site — Teachings, Newsletter, Aviv Reports, Contact all redesigned to match.

I can mock up:

• The Teachings index + a single teaching page
• The Newsletter signup + archive
• The Aviv Reports landing
• Article/post template

Then you'd either:

• Migrate to a static-site generator (fastest, cheapest hosting, but loses WP's editor)
• Rebuild as a custom WordPress theme using these designs (keeps WP editor, more dev work)
• Move to a headless CMS (modern, best UX, but a real migration)

Pros: Coherent brand throughout. Modern site. Cons: Real project — weeks of work, content migration, choosing a stack.

My recommendation

Do this in three steps:

1. First — let me design the moon-sighting admin page so you can see it. 30 minutes of work.
2. Then — let me design the next 2–3 key pages (Teachings index, single teaching page) in this same visual language so you can see if the system holds up beyond the homepage.
3. Then decide between Path A (ship the homepage now) and Path B (full rebuild).

Want to start with the admin button mockup?

Perfect plan. Let me bundle the page into a single self-contained HTML file, then build the admin reset page.

<!-- -->

<!-- -->

<!-- -->

<!-- -->

<!-- -->

Bundle works clean. Now let me build the admin reset page.

<!-- -->

<!-- -->

Now let me bundle the admin page too so you can drop both files on the server:

<!-- -->

<!-- -->

Both files are ready to download above.

Quick install notes:

1. Homepage (sightedmoon-homepage.html) — rename to index.html on your server, set as homepage. Update the "Enter The Site" link to point to your existing WordPress home, and the "New to SightedMoon" link to your new beginner page.

2. Admin (sightedmoon-admin.html) — put it at a non-obvious URL (e.g. /admin-moon-2026.html) and protect with .htaccess basic auth or your host's password protection. Currently uses localStorage (only persists on the device that pressed the button), so you'll need a developer to swap the localStorage calls for a tiny backend endpoint — the code has comments marking exactly where. Until then it works as a UI prototype.

3. For the homepage to actually use the sighting date, the same backend endpoint needs to be added — also marked in the code.

When you're ready, send me the developer's questions or have them ping me and I'll spec the endpoint exactly.

<!-- -->

<!-- -->

Good — I have the structure. For Divi 5, I'll create a guide that breaks the page into Divi-friendly sections you can paste into Code Modules. Let me build that now.

<!-- -->

I have enough of the structure now. Let me build a Divi-friendly export that breaks the page into clean, copy-paste-ready sections.

Now let me read the rest of index.html so I can split it into the section files faithfully.

Now I have everything. Let me build a clean, Divi-friendly version. The key insight: a real production page doesn't need the Tweaks panel or all the variations — it just needs the live moon, logo, copy, and CTAs. Let me write the section files plus a complete full-page.html.

Now let me create the modular section files. The key change vs. the working homepage: I prefixed every CSS class with sm- so they don't conflict with Divi's own styles, and I removed the Tweaks panel + the Tweaks-only behaviors (date stepper, button-style switcher, gold-tone switcher, background switcher).

Now let me verify the full-page version actually works by previewing it, then package the folder for download.

Good nudge — let me hand off properly.

Download is ready above ⬆️

The pack contains a README plus 9 HTML files. Quickest path: open full-page.html, copy everything, paste into one Divi Code Module — done. README has the modular path if you'd rather break it up.

Human: [id:m0293]

I'll update the about copy in all three places (homepage, full-page Divi export, and modular Divi section). With the wording you gave, the bolded <em> keywords no longer fit the new sentence — I'll highlight "Biblical calendar" and "Jubilee cycles" instead since those are the core concepts.

Now let me also rebuild the bundled single-file version so it stays in sync.

Updated the about copy in all three places (live homepage, Divi full-page export, and modular Divi section file), plus rebuilt the bundled sightedmoon-homepage.html so it's in sync. The new sentence highlights "Biblical calendar" and "Jubilee cycles" in gold.

30% smaller: 462 × 0.7 ≈ 323px, 55vmin × 0.7 ≈ 38.5vmin. Mobile: 72vmin → ~50vmin.

Moon is now 30% smaller across the homepage, the Divi full-page export, the modular section-1 styles, and the rebuilt single-file bundle.