A new website for a Chișinău kindergarten, with a simple panel where the team publishes events on its own and receives parents' requests

The business problem

Startica already had a website, with a clear visual identity that parents recognised. For a private kindergarten, the website is the first place where a parent decides whether to book a visit. Events (celebrations, trips, workshops) show daily life at the kindergarten and need to reach the site quickly, with photos.

The event photos, however, sat on the old server, which refused to show them on another domain, so they could not simply be moved. And an enrolment request that does not reach someone on the team quickly can mean a lost place.

To find, together with the client, a way to keep the website parents know while handing control to the kindergarten's team, so events go live without a developer and no request gets lost.

• Same face, new platformParents should not notice the switch: every page was compared with the original, element by element
• Photos locked on the old serverThe old server refused images shown on another domain; the photos were moved into the client's own storage
• Non-technical usersKindergarten staff publish events: the panel asks only for title, date, text and photos
• Personal dataThe forms collect names, phone numbers and the child's age, and the data goes only to the team, never exposed publicly
• Drafts vs. publishedA half-written event must not appear on the site
• More languages laterEvent content is prepared for RO, RU and EN, so expanding won't require a rebuild

The solution

We did not start with screens. We started with the existing site: we went through it page by page and built a complete inventory of its content, from copy and photos to age groups, schedules, spaces and events. Then we traced how information moves: who publishes an event, who receives an enrolment request and what they do with it. That became a requirements document capturing the decisions made with the client: what stays the same, what moves into the team's hands, and where requests land.

We first rebuilt the site identical to the original, and only once the identity was signed off did we move on to improvements. The panel holds only events, the one kind of content that changes often; the other pages stay fixed so the panel stays simple. "Book a visit" opens the form on the same page, so the parent is not pulled away from what they were reading, and the request lands on Telegram, on the administrator's phone.

What we found midway through

The site has many photos, and parents open it mostly on their phones. We optimised images into modern formats and sizes suited to each screen, so galleries load quickly on mobile data too.

Content in three languages called for a structure where each page and gallery is managed once, with the copy translated separately.

The initial structure spread the information across separate pages. We moved groups, programmes and spaces onto the home page, so parents see everything in one pass without hunting through the menu.

What the client gained

The Startica team now publishes events with photos on its own, without waiting for a developer. Parents' requests reach the administrator's phone right away, and the visit form is one click away from any page.

The site's photos and data live in the client's own accounts, not on the old server. For parents, the site looks the same as before, only built to load well on phones too.

After launch, Codepedia provides 6 months of maintenance: we fix bugs and handle anything unexpected, so the kindergarten's team can stay focused on the children.

What it looks like

From the blog