About this demo
This site was built to accompany I A Expand LLC's response to TUSD RFP 27-023-TUSD1 (District Website Platform). It demonstrates the shape of the proposed platform, not the production build.
What's real vs. representative
| Area | In this demo | In the proposed production build |
|---|---|---|
| Data storage | Hardcoded Python data, held in memory; resets on restart | PostgreSQL with Wagtail page models, revisions, and permissions |
| CMS | Flask + Jinja templates | Django + Wagtail CMS |
| Accounts | Five fixed demo logins, one shared password | Microsoft Entra ID / Azure AD SSO, SAML, MFA |
| Workflow | Draft → Review → Approval → Publish, enforced in code | Same states, configurable per site, with notifications and escalation |
| Accessibility | Issues are pre-assigned to sample content to show the guardrail | Automated scanning on upload and on a recurring schedule |
| Broken links | A fixed sample list | Scheduled crawl with a real work queue |
| Search | Substring match over the sample content | Indexed search with filters, facets, and analytics |
| Integrations | Not connected | ParentSquare, Synergy, Tyler iVisions, Google Workspace, M365, GA/GTM, KickUp |
| Hosting | Single container on Render, for demo purposes | Redundant US-based containers, documented in the technical proposal |
What to click on
- The district home page and three school sites show branding-per-site and syndicated announcements.
- Log in as any of the five demo accounts to see role-scoped dashboards.
- Open a content item and move it through the workflow to see the accessibility publishing guardrail in action.
- The Accessibility and Broken Links pages under the dashboard show the reporting views.