Center staff now update the website themselves, signed in with Microsoft.

The work

What we built, and why

The starting point

The client runs inclusive early learning centers in North Carolina, where children with and without disabilities learn side by side. A WordPress rebuild of the center's website had been staged with a hosting company, and the client asked us to finish it and put it into service.

Our review of that build came first. Its robots file told Google not to read any page. The three forms were placeholders, the events calendar was empty, and the weather banner was hard-coded to say the center was open. Images carried no descriptions, and nothing on the site needed WordPress to run.

What we built

We moved the site off WordPress to a static site in the client's own Azure tenant, so the organization owns the hosting, the code, and the data. The approved copy stayed word for word, and the design was rebuilt to match the parent organization's brand: its navy and orange, its type, and a clear main action on every page.

The home page carries the 2026 tour video, which loads only when a parent presses play. That one change, with image and script work, moved the mobile performance score from 58 to 87.

How we built it

We built the site with the AI-assisted development method we use on our own work. AI coding agents write and revise the code under written project rules that set the brand, the copy that may not change, and what must never be published. Every change runs through automated tests and accessibility checks before it ships, and a person reviews each result.

That method is why the project moved quickly. Work started on 17 September 2026, and the client approved the finished design on 1 October, two weeks later, with the staff editor already working.

Search and AI answers

Every page has its own title, description, canonical address, and share image. The sitemap lists the public pages, and the robots file now invites search engines in while keeping the editor out.

For AI search, an llms.txt file describes each page in plain language. Structured data tells search engines and AI assistants that this is a childcare center, where it is, and when it is open. Lighthouse on the home page moved from 92 to 100 for search, 96 to 100 for accessibility, and 93 to 100 for best practices.

The staff editor

The part parents rely on most is what changes daily: closings for weather, the menu, events, and open jobs. Center staff now change those themselves in a private editor, signed in with their own Microsoft work accounts. There are no separate passwords to issue or reset.

Saved changes appear on the public pages straight away, with no developer and no redeploy. Messages from the three forms arrive in an inbox inside the editor, and a backup page lets staff save and restore everything they manage. The editor is hidden from search engines and from the AI guide, and only invited staff accounts can open it.