Private kindergarten or school website: daily routine, team, enrolment

Parents choose a kindergarten well in advance and compare carefully: they read everything, look at every photograph and ask other parents. A private kindergarten website has to give them enough information to make them want to come for a visit, because the decision is made there, in the classroom, not on a screen.

All of it is done with a degree of care that other sectors do not call for: children may appear on the site. Photographs, names and any information about minors are published only with the parents’ consent, and as little of it as possible. Many of the technical choices follow from this.

What a parent wants to find out before ringing

There is usually a site made when the kindergarten opened, with a paragraph about “a warm and friendly environment” and an old gallery. What is missing is exactly what parents care about: what time children are dropped off and collected, how many children there are in a group, who the teachers are, what the children eat, whether they nap at midday, what happens when a child has a cold.

The same questions then reach the head by phone, in the middle of the day. The structure we propose takes them one by one and answers them in writing, so that the visit is about the child and the place, not the timetable.

Private kindergarten website: the pages that answer before the visit

We explain the educational approach in concrete terms. If you follow an alternative pedagogy or work in two languages, the page shows what that looks like on an ordinary day, not just the name of the method. Authorisation or accreditation status appears exactly as it stands in the documents.

On fees we write nothing on your behalf: the page shows what is included, what is paid for separately (meals, optional activities, transport) and how payment is made. Whether you also publish the amounts remains your decision.

• The daily routine: arrival, activities, meals, nap, optional activities, departure, by age group.
• The team: teachers, care assistants, psychologist, the teachers of the optional activities, each with their training.
• The premises: classrooms, yard, play area, kitchen, photographed without children.
• Enrolment steps: visit, documents, contract, settling-in period.
• The weekly menu: a page the kitchen can change easily.
• Frequently asked questions: illness, absences, holidays, extended hours.

Booking a visit and the year’s calendar

The visit form asks for little: the parent’s name, a phone number, the child’s year of birth, the preferred group, the date from which a place would be needed and two possible time slots for the visit. It does not ask for a personal identification number, certificates or medical information; those are handed in at enrolment, on paper or through the channel the kindergarten has set.

The calendar brings together holidays, days off, children’s shows, parents’ meetings and open days. Each event is added from the admin panel and drops off the list by itself once it has passed. For schools we add the enrolment periods and, where relevant, the assessments.

The area for parents whose children are already enrolled (announcements, photos from activities) is a separate matter. Often a communication app made for the purpose is a better fit than a password-protected section of the site.

Photographs of children and minors’ data

The basic rule: no image in which a child can be recognised is published without the parents’ written consent, requested separately for the site and for social media. The form of the consent and the retention rules are something you settle with your data protection officer or with a lawyer. We build the site so that the rule is easy to follow.

We recommend that the presentation rest on spaces, materials and activities seen close up (hands modelling clay, drawings, the garden), not on portraits.

• No names next to faces: no caption that identifies a child.
• Fast removal: any photograph is taken down from the admin panel on the spot, including from the site’s cache; it disappears from Google results with a delay.
• No hidden data: we add a step that strips location data from photo files on upload, because WordPress keeps the original unchanged.
• Short galleries: a few chosen images, not hundreds of photos from the children’s show.
• Limited access: only designated people can publish images.

The platform, the stages of work and what the site cannot do

The platform is WordPress, with a theme we write ourselves, compatible with Elementor Pro (a visual editor) and with separate content types for the team, events and the menu. We add structured data, meaning a description of the institution in a format read by Google: name, address, opening hours, phone number.

The site does not replace other parents’ recommendations, nor the visit. You judge it by the number of visits booked through the form and by how often you still get phone questions that the pages already answer.

• A conversation with the head and, ideally, with two parents: what they looked for and did not find.
• Structure and copy, checked by the institution’s management.
• A planned photo shoot, with the consents collected beforehand.
• A warm but uncluttered design, legible on a phone.
• Testing the form, the calendar and the publishing permissions.
• Training for the person who will update the menu and the events.

This is a typical project description: it shows how we usually approach this kind of work and does not present a project carried out for a particular client. Every real project starts from your company’s situation, and the stages, timescales and price are agreed after the initial discussion.