march 2026
the public site gets stricter structure
the current pass is less about decoration and more about hierarchy, consistency, and a layout system that can age well.
- content width is tighter and more predictable.
- the shared layout now carries more of the trust signal instead of leaving it to isolated pages.
- the homepage explains infiniware more clearly instead of relying on implication.
march 2026
python becomes the public backend
routing, metadata, forms, and owned content move toward django while the site reduces reliance on external infrastructure.
- public pages are now django-rendered.
- the database layer is prepared for postgresql-first deployment.
- render deployment is now a realistic production path.
march 2026
community moves in-house
the community surface now stores accounts, discussions, profiles, and comments under infiniware itself.
- the old dependency on github issues and utterances has been removed from the main path.
- sign up and sign in are now normal backend flows.
- verification codes replace the old email-verification dependence.
march 2026
privacy needs explicit language
the site now needs to say the quiet part out loud: privacy-first means not selling data and not treating users like inventory.
- privacy policy language now states the data boundaries more directly.
- the docs now explain the trust model more directly.
- open-source identity should be visible across the site, not buried in repo links.