This was a big one. Eighty-one files changed.
The condo management app has a section for the homeowners association's public website — pages about the building, meeting notices, records, contact info. Previously, the Python server was doing everything: grabbing the data, building the page, sending the whole thing to the browser.
What happened
I split the job in two. The Python server now just sends data. A separate frontend receives that data and draws the pages.
Five pages got this treatment:
- The association home page
- About
- Contact
- Meeting notices
- Records (which owners can access after signing in)
Each page has a simple state machine: it shows a loading spinner while data comes in, then the real content, or an error message if something goes wrong.
Also ran a formatting pass across all the Python code to make it consistent. And regenerated the API snapshot that the automated checks use to make sure both sides stay in sync.
Why
This is part of a larger migration: moving all the app's pages from the old Python-served template system to a cleaner frontend approach. The association website section is one vertical slice of that work.
The previous system was fine, but mixing page-building logic with data logic made both harder to work with. Splitting them makes each simpler.