Skip to content
GPLWP Guides

How to create a kindergarten website in WordPress

Design & LayoutWordPress Time About 2–4 hours 6 steps Updated 20 Sep 2026

DESIGN & LAYOUT
The short answer

Create the main pages first, then set a static homepage, build the header and navigation, and style the site with WordPress blocks or a page builder. WordPress can handle the basic site without a plugin, but events, registrations and advanced forms need extra tools.

The route
  1. 01Plan the pages and content
  2. 02Choose the manual design route
  3. 03Build the main homepage
  4. 04Set the homepage and menu
  5. 05Add events and contact tools
  6. 06Use Toddly for the fast route

What you need

  • A WordPress website with administrator access
  • Your kindergarten logo, colours, text and approved photographs
  • A list of programmes, opening hours, fees and contact details
  • A privacy policy and consent process for collecting enquiries and publishing children’s photographs

Plan the pages and content

Write down the information parents need before choosing colours or adding decorative sections. A useful starting structure is Home, About, Programmes, Admissions, Events and Contact. Add a separate page for fees, term dates, staff or FAQs only when that information needs room of its own.

Prepare a short welcome message, clear calls to action such as “Arrange a visit” and “Ask about a place”, your phone number, email address, location and opening hours. Keep children’s names and identifying details out of public content unless you have a specific, documented reason to publish them.

Choose the manual design route

For a small site, use a well-supported WordPress theme and the block editor. Create each page from Pages > Add New, then use headings, columns, buttons, image, gallery, cover and group blocks to assemble the layout. WordPress pages are intended for non-chronological information such as About, Contact and Privacy Policy pages.

If you use a block theme, edit the global header, footer, colours, typography and navigation in Appearance > Editor. The Site Editor applies changes to shared templates across the site, so changing the header there can affect every page. With a classic theme, use its Customizer or theme settings instead.

This manual route is fine when you have a simple brochure site and want fewer dependencies. The drawback is that you must design every page yourself, and events, enrolment workflows and complex forms will usually require separate plugins.

Build the main homepage

Put the most important decision-making information near the top: what age groups you accept, where you are, your next enrolment date and one primary action. Follow it with short programme cards, a brief introduction, an events or news area, a visit invitation and contact details.

Use one consistent content width, a small colour palette and no more than two typefaces. Give buttons descriptive labels, keep body text readable, and use real, approved photographs rather than filling the page with stock images. Add meaningful alternative text to informative images and leave decorative images empty, as recommended in the WordPress Image block documentation.

Set the homepage and menu

Publish the pages, then go to Settings > Reading and choose a static page for the homepage. Select a separate page for posts if you plan to publish news. On a block theme, check the Front Page template as well: a front-page template can take precedence over the Reading setting.

Add the key pages to the header navigation and place less-used links, such as Privacy Policy and staff vacancies, in the footer. Block themes manage menus through the Navigation block or Site Editor; classic themes may use Appearance > Menus. Only published pages appear as usable navigation items in the Navigation block.

Add events and contact tools

You can publish a basic events list as normal pages or posts, but a calendar, recurring events, registration limits, reminders or payments need an events or booking plugin. Add a simple contact form with fields for the parent’s name, email, phone, child’s age group, preferred visit date and message. Do not ask for more personal information than you need.

Before launch, submit the form yourself, check that notifications arrive, test the calendar on a phone and confirm that event links appear in the menu. If an event calendar suddenly loses styling or stops showing events, test with caching disabled and then deactivate other plugins one at a time; support threads repeatedly identify theme and plugin conflicts as common causes.

Use Settings > Privacy to create or assign a privacy policy, then review the data collected by forms, analytics, maps and embedded media. WordPress notes that its built-in privacy tools do not cover every third-party service.

Use Toddly for the fast route

If you want the design assembled faster, use Toddly, a kindergarten-focused WordPress theme with child-oriented layouts, event tools and Elementor support. Install the theme through Appearance > Themes, activate it, install any required companion plugins, and import its starter layout if one is supplied.

Replace the demo logo, photographs, text, contact details and events before publishing. Review the header, footer, mobile layout, forms and page URLs rather than assuming the imported content is ready. Elementor supports importing website templates and selecting templates, content and site settings, but importing a kit onto an existing site can overwrite or append site data, so make a backup first.

The fast route

Let Toddly do it

Purpose-built kindergarten layouts with event tools and Elementor support; choose it for a child-focused school site.

Get Toddly

Sources

  1. wordpress.org /documentation/article/create-pages/?utm_source=openai
  2. wordpress.org /documentation/article/site-editor/?utm_source=openai
  3. wordpress.org /documentation/article/image-block/?utm_source=openai
  4. wordpress.org /documentation/article/additional-guide-to-using-the-site-ed…
  5. wordpress.org /documentation/article/navigation-block/?utm_source=openai
  6. wordpress.org /support/topic/events-not-showing-try-these-first/?utm_sourc…
  7. wordpress.org /documentation/article/wordpress-privacy/?utm_source=openai
  8. elementor.com /help/import-and-export-elementor-website-templates/?utm_sou…

Questions

Can I create a kindergarten website in WordPress without a plugin?
Yes, you can create the pages, homepage, navigation, images and basic contact details with WordPress itself. A plugin becomes useful or necessary for features such as a calendar, event registration, online payments, advanced forms, staff directories or parent portals. For a simple information site, the block editor and a suitable theme are enough.
What pages should a kindergarten website include?
A kindergarten website should usually include Home, About, Programmes, Admissions, Events and Contact pages. Add fees, term dates, FAQs, staff information and policies when parents need those details regularly. Keep the main navigation short, then place privacy, safeguarding and less frequently used information in the footer or a secondary menu.
How do I make the homepage show first in WordPress?
Create and publish a Home page, then choose it as the static homepage under Settings > Reading. If the site uses a block theme, also inspect the Front Page template in Appearance > Editor because that template can control the front page independently of the Reading setting.
Why is my kindergarten events calendar not displaying correctly?
The usual causes are a theme conflict, another plugin, stale caching or incorrect calendar settings. Clear the relevant cache, check the calendar’s page and shortcode or block, then test with other plugins disabled. If the calendar works with a default theme, the active theme is likely affecting its layout or scripts.
How should I use children’s photographs on the website?
Use photographs only when the kindergarten has the appropriate written permission and a clear reason for publishing them. Avoid names, locations, routines and other details that could identify a child, and review old media regularly. Also check your privacy policy and any consent requirements for forms, analytics, maps and embedded services before launch.