The short version
Last week I pointed a full review at this site: every page, in both languages, on a phone and on a computer, plus the machine-readable side that AI assistants use. Then we fixed what it found: two pull requests and seventeen commits' worth. Here's what changed, including two bugs of our own — glad we caught them, not glad we shipped them.
Board policies, now in Spanish
The district's 619 board policies, bylaws, and regulations have been browsable on this site since May, but only in English. Now there's /politicas/: every policy title translated to Spanish, searchable in Spanish. Type uniformes and you get the dress code policy; type vacunas and you get immunizations. The full policy text is still English-only for now, and the page says so up front. But finding the right policy no longer requires knowing its English name.
Who teaches at your school
Every school page has a new section: how many teachers work there, how long they've been teaching, how many are in their first or second year, students per teacher, students per counselor, and the racial and ethnic makeup of the teaching staff. It's all California Department of Education data for 2024-25, and where the state hides small numbers to protect privacy, the page says "fewer than 10" instead of pretending the answer is zero.
The two mistakes
While building that section we found a real error in our own data: the site's Long-Term English Learner counts were exactly double the truth. The state's file lists every grade three times — girls, boys, and everyone together — and our pipeline added all three, so every number came out at twice reality. The dataset said 15,046 students when the real count is 7,523. It's fixed at the source and the published numbers are correct now. I also wrote down how the trap works, so the next state dataset we add gets checked for it. If you (or your AI assistant) pulled English Learner numbers from this site before June 10, throw them out and look again.
Separately: 22 of the Spanish meeting transcripts had been silently corrupted on our file server for months. A Spanish-speaking reader opening those meetings got an error message where an English reader got a transcript. That's backwards from what this site is for. All 22 are repaired, and the publishing pipeline now refuses to upload a transcript that fails validation, so this particular failure can't happen quietly again.
Much better on a phone
A parent told us they couldn't find the search box on their phone. They were right: at some screen widths it slid clean off the edge, and the navigation showed three tabs while hiding the rest with no hint there was more. Both fixed: the menu now wraps so every section is visible, the search box stays put down to the smallest phones, school pages no longer scroll sideways, and the little links on the homepage school cards grew from 15 pixels tall to something a thumb can actually hit.
We also went through the site swapping jargon for plain words ("42% learning English · 63% free or low-cost lunch" instead of "42% EL · 63% FRL"), and search results now tell the truth about themselves: if there are 75 matches and you're seeing the best 20, it says so.
For the technically curious
AI assistants got four new tools on the MCP server: board members, document search, meeting lists, and transcript search within a single meeting. Every AI-generated summary the server returns now says so. The data bucket at data.rcsd.info has a machine-readable index. GitHub's security scanner is at zero open findings after a hardening pass. And there's now a CHANGELOG recording what changed when, going back to the site's launch in March. From the same stretch of work: the district page now introduces your five board trustees with photos, areas, and terms, and there are dedicated pages for district committees like the bond oversight committee (CBOC) and DELAC.
Found something off?
This tune-up started with a review and a parent's complaint, and both made the site better. If something looks wrong — a number that doesn't add up, a broken page, clumsy Spanish — tell me: [email protected], or open an issue on GitHub.