HV Tech Stack Chapter 01 · Stack
Every component in the platform. What it does. What it costs. Who owns it.
I.
Part One
A hub in the middle. Spokes at the edges. A traffic cop between them.
Heritage Village runs on a hub-and-spoke model. Microsoft Dataverse is the hub. WordPress, MaintainX, Constant Contact, WebTrac, and libib are spokes. Power Automate is the traffic cop between them. Teams and SharePoint handle staff surfaces. SendGrid or Mailgun carries transactional email.
II.
Part Two
Nine pieces carry the platform. Each does one job well.
The public website and gated resident portal. A custom theme built from vanilla HTML, CSS, and JavaScript. Staff edit content through a stripped-down admin. The theme disables Gutenberg on locked pages and enables it on the editorial blog.
Strict form fields replace the open text editor. Staff see labeled inputs for headline, date, committee, PDF, and meeting video. The layout stays locked.
The master database. Holds the resident roster, unit ownership, approved vehicles, variance records, work-order history mirrored from MaintainX, and every form submission. One brain. One source of truth for operational data.
The middleware between every spoke. Triggers on webhooks, database events, and schedules. Translates payloads. Prevents infinite loops by checking the service-account author on every sync.
Work orders for trades and office staff. Already in heavy daily use. Stays in place.
Calendar, class sign-ups, and space bookings. Already in place. Residents click through; the portal does not wrap it.
/living-here/activities; the homepage pulls a lightweight event feed where the vendor supports it.The e-Bulletin newsletter provider. Sends to opted-in residents.
Library catalog for the community library.
/living-here/facilities/library.Delivers magic-link emails, form confirmations, and staff notifications. Pairs with WP Mail SMTP. SendGrid or Mailgun both fit.
III.
Part Three
Where the people who run the place actually work.
Every staff member lives here. Premium licenses go to builders. Standard licenses get Adaptive Cards.
The reporting tier for tier-3 staff. Power Automate writes nightly upserts to Excel files on SharePoint. Staff open the files through their standard M365 license.
Single sign-on for staff. Binds to Dataverse and Power Apps.
IV.
Part Four
Three tiers. Each maps to a Microsoft license level.
See Auth for the full role table.
V.
Part Five
The whole stack on one page. Twelve rows, one sentence apiece.
| Layer | Component | Cost / year | Owner |
|---|---|---|---|
| Frontend | WordPress custom theme | $0 core | HV IT |
| Forms | ACF Pro | $49 | HV IT |
| Hub DB | Microsoft Dataverse | license-based | Nate |
| Middleware | Power Automate | license-based | Nate |
| Trades | MaintainX | existing | Ops |
| Events | WebTrac | existing | Activities |
| Newsletter | Constant Contact | existing | Comms |
| Library | libib | existing | Volunteers |
| SendGrid or Mailgun | ~$240 | HV IT | |
| Staff chat | Teams | M365 | HV IT |
| Reporting | SharePoint + Excel | M365 | HV IT |
| Identity | Entra ID | M365 | HV IT |
Hosting platform choice lives in Operations. The plugin list beyond ACF Pro lives in Auth. The design system (typography, palette) is locked in the design-system folder.