TCR Website

Overview

Status: active deployment, blocked on DNS until fall. TCR’s public website, live at tcrtek.org, built with Astro, Tailwind, and React. Beyond content pages, it includes a chatbot and multiple forms that feed into n8n and Tally for handling.

Technology

• Framework: Astro
• Styling: Tailwind
• Interactive components: React
• Hosting: SiteGround
• Backend: Cloudflare Workers + D1 + KV; n8n for workflow automation
• Forms/chatbot handoff: Tally
• Repo: github.com/waderk1986/tcr-full-site (HTTPS remote). Local working directory astro-tcr-web, developed on a Mac — a separate project from the documentation-system repo this docs site lives in.

Background & why

The previous site ran on WordPress, and the overhead was a real problem: slow loading times, broken links, “ghost” links (pointing at nothing), and no real customization ability. The current Astro/Tailwind/React site was built to fix all of that — it’s modern, snappy/fast, gives full control over the codebase, is far more user-friendly, and was built with accessibility in mind from the start. It’s also meaningfully easier to connect into the rest of TCR’s ecosystem through n8n than WordPress ever was.

Not yet documented: exact build/launch date.

DNS blocker

DCSD (the district) controls tcr.edu DNS via its own nameservers — not TCR-managed. District IT is out for summer, which blocks standing up Cloudflare Worker routes for tcr.edu/api/* until fall. Interim workarounds and the fall cutover plan were meant to be tracked in a MISSION_CONTROL.md doc in the tcr-full-site repo, but that file wasn’t found in the local checkout as of 2026-08-19 — worth confirming where it actually lives, or recreating it, since it’s referenced as the source of truth for this cutover.

Chatbot

A chatbot on the website is scoped to answer only using the website’s own content — it doesn’t reach into other systems. When a visitor needs a human, the conversation hands off to a Tally form.

Forms & routing

The website has several forms beyond the chatbot handoff. Form submissions go through Tally, and n8n routes them to the correct internal inbox by category:

• Maintenance requests
• Attendance alerts
• IT help desk
• General questions

Not yet documented: the full list of forms on the site, and which of them (if any) feed into Populi directly rather than just routing to an inbox.

Access

Not yet documented: hosting/deployment access, who can edit site content, admin access to the Tally forms and chatbot configuration.

Dependencies

Depends on Tally (form capture) and n8n (routing) to turn a form submission or chatbot escalation into an actual email reaching a department.

Backup & recovery

Not yet documented.

Notes

See n8n for how form/chatbot submissions get routed once they leave this site.