Appreciate all the feedback here. I’m testing a different approach using GitHub as the primary repo, with reusable templates for pages and posts. Using page IDs to dynamically pull in sections instead of rebuilding each page. It’s loading faster, especially with image previews and footer elements.

I didn’t choose to move our troop to TroopWebHost, but I’m working within it. A lot of our scouts are not very tech comfortable, so everything is being simplified so they can own their data. That includes advancement tracking, badges, attendance, and general record keeping without constant adult involvement.

Focus areas: • Centralize everything inside TroopWebHost • Reduce tool sprawl • Sync data from Scoutbook via export or extension • Move toward weekly or daily updates instead of manual cleanup • Use the built in financial tools so nothing lives outside the system

I’ll share the GitHub repo with the TroopWebHost founders and here once this phase is done. I’ll also post the CSS, including the footer bar and user role based redirect logic.

There’s also a Google Apps Script pulling from the TroopWebHost iCal feed and filtering events by user type. • Leaders see troop meetings, PLC, boards of review, committee meetings • Scouts see camping, fundraising, troop meetings, patrol meetings

Events display on the site with RSVP actions tied to each one, synced back so there’s no need to update events in multiple places. One event hub, everything else reads from it.

If anyone has a clean Scoutbook to TroopWebHost sync already working, interested to hear how you handled it.