CN All projects
Polski
Let's talk

Czarodziejskie Smyczki

A preschool site built around a parent's decision.

I rebuilt the website of Czarodziejskie Smyczki, a music preschool, because the old version didn't show what matters most about the place: the people, the atmosphere and the way the staff work with children.

The first screen of the new Czarodziejskie Smyczki website: a heading about a child's independence, the buttons Enroll your child and See how we live, and next to them a photo of a teacher playing the ukulele for children
The first screen of the new website, live since June 9, 2026. Screenshot from September 23, 2026, 1440 px. The website is in Polish.
Role
Content, structure, design, build
Time
1.5–2 weeks
Launch
June 9, 2026
Tools
Figma, Antigravity, Cloudflare
Status
Live at czarodziejskiesmyczki.pl

Starting point

The old site said a lot, but showed very little.

I didn't start by asking how to make a prettier interface.

First I wanted to understand what wasn't working in a parent's first contact with the preschool. The old site read like a long document, the contact details were hard to find and the gallery was empty. Parents got information, but they didn't get a clear picture of the place.

Four pairs of full-page screenshots at 1440 px. Pick a page and scroll the frame: you'll go through both versions, from header to footer, at the same scale.

The old Czarodziejskie Smyczki home page from the Web Archive, full-page screenshot
Before, copy from May 21, 2026 A long document

Below a photo with a Montessori slogan, the text just keeps going: the offer, full staff bios, the daily schedule and a list of celebrations. 11,441 px tall.

Open screenshot in a new tab
The new Czarodziejskie Smyczki home page, full-page screenshot
After, since June 9, 2026 Getting to know the place step by step

A parent's worries, settling in, a day at the preschool, photos, reviews and questions, each in its own section. 6,880 px at the same width.

Open screenshot in a new tab

The staff bios moved to “About us”, so the home page got shorter without losing any content. What stayed is what helps a parent decide whether they want to get to know the place better.

The old Passion for Learning page from the Web Archive, full-page screenshot
Before: “Passion for Learning”, March 16, 2026 An approach described in text

Montessori, music and dance as columns of text. The empty frames on the right are photos the archive didn't keep.

Open screenshot in a new tab
The new About us page, full-page screenshot
After: “About us” An approach shown through people

The philosophy in three points, a photo from a classroom, initiatives and certificates, and below them thirteen members of staff.

Open screenshot in a new tab

The old site spread the approach across three pages: Passion for Learning, Music Therapy and Healthy Habits. The new one brings them together in one place, next to the people who put them into practice.

The old Gallery page from the Web Archive: its only content is the line No current galleries
Before: “Gallery”, March 16, 2026 “No current galleries.”

The entire content of the page that was meant to show the preschool.

Open screenshot in a new tab
The new Gallery page with six photos of everyday preschool life and a More photos button
After: “Gallery” 32 photos of everyday life

Six to start with and a button that loads more.

Open screenshot in a new tab

The simplest pair in this set and the most tangible result of the project.

The old Information page from the Web Archive, full-page screenshot
Before: “Information”, March 16, 2026 Contact below the announcements

The old site had no contact page. Enrollment, the phone number and the application form sat at the bottom of “Information”, below a long series of notices.

Open screenshot in a new tab
The new Contact page: phone, email, opening hours and a map on the left, a form and a PDF application form on the right
After: “Contact” Contact options side by side

Phone, email and opening hours on the left, the form on the right, and below it a PDF application form to print.

Open screenshot in a new tab

A parent doesn't have to look for where to sign up. They only choose how.

About the “before” screenshots. These are the last Web Archive copies from before June 9, 2026. The archive didn't keep the icon font or some of the photos, which is why the menu shows empty squares and the pages show empty frames. It didn't look like that live. I took the “after” screenshots on September 23, 2026 from the working site.

Text first

First, I wrote the website.

From NUEVE I took a rule I keep coming back to: a website has to be written first and checked for how well it reads. Only then comes the visual layer.

The Smyczki commission came at a moment when I was practicing this direction anyway. Two weeks earlier I had designed a parent dashboard for a therapy center as a personal exercise, so I had the look ready before the client got in touch. I still wrote the text first, because the text decided which of those patterns made sense for a preschool.

I laid the website out as a calm way of getting to know the preschool.

  1. 01What Smyczki is
  2. 02Settling in
  3. 03The Montessori approach
  4. 04Real photos
  5. 05Staff
  6. 06FAQ
  7. 07Contact
Two buttons from the first screen: a filled Enroll your child and an outlined See how we live

I left two paths on the first screen.

I didn't want to assume that every parent arrives at the same stage of the decision.

“Enroll your child” → Contact

Leads straight to contact.

“See how we live” → About us

Lets parents get to know the place and the people first.

The hammer and the smith

AI was the hammer, but the direction was mine.

I made Smyczki early in my work with AI coding tools. AI sped up the execution, but the diagnosis, the choices and the responsibility were mine.

  1. Exploration, before the commission came in

    I was preparing screens for a parent dashboard for children's therapy in Google Stitch and marking on them what stays and what goes.

    A board in Figma: five parent dashboard screens from Google Stitch with handwritten underlines, ticks, crosses and three purple sticky notes
    My board in Figma: the screens come from Google Stitch, the markings and sticky notes are mine. Working notes, left as they were. Tick: I'm taking it, cross: I'm dropping it. The notes below are translated from Polish.
    • “All very neat, but every bit of this would need wiring up and building a login system for the site, and at that point we're making a kind of web app! interesting but insanely demanding.”

      Cost of building it
    • “kinda cool, but also a tough one: how many of these ‘progress’ steps would there be, and the scale, if anything, should go up to 5, not 4.”

      Does the scale make sense
    • “Super nice greeting, and the problem of personalizing the message goes away”

      The problem this pattern solves
  2. A parent dashboard for the drawer

    From what was left, I designed my own parent dashboard in Figma: two menu states and my own components. It was an exercise nobody but me ever saw. I put in the SensoBaza name as a placeholder, because I had worked with it before.

    What carried over from the exercise to Smyczki

    A heading in two registers
    The second line in italics in the accent color: in the exercise “See how Liam is blossoming today”, on Smyczki “Galeria Magicznych Momentów” (Gallery of Magical Moments).
    A label in a pill
    “Upcoming visit” above a card in the dashboard, “Our everyday life” above the gallery heading.
    Soft cards on a warm background
    Strongly rounded, with no hard borders.
    An icon in a tinted circle
    Next to the weekly summary in the dashboard, and next to the phone, email and opening hours on the Smyczki contact page.
    Pill-shaped buttons
    The primary one filled, the secondary one outlined or text-only.
    The color didn't carry over
    brown #925531 in the exercise, the Smyczki green #8EB085.
  3. Text and structure

    I gathered references, wrote the content, laid out the pages and defined the role of each section.

  4. Code

    Antigravity helped me turn those decisions into code. When I didn't understand something, I kept asking what we were changing and why.

  5. Review and launch

    I ran the project locally, checked how it responded to different screens and came back with fixes. Then came the launch on Cloudflare and more fixes after it went live.

Three decisions

Three small decisions revealed how the preschool really works.

The Our Staff section on the About us page, teacher cards with photos and roles

Staff higher up

On the “About us” page I moved the staff higher. For a parent, seeing the people they'll be trusting their child to mattered more than another description of a therapy.

The Little Heroes Academy certificate opened enlarged over the dimmed page

Certificates in a light gallery

At Ms. Ewa's suggestion I added four certificates in a light gallery with a zoom view. They aren't staff diplomas but traces of initiatives the preschool takes part in: first aid, environmental protection, helping animals. They were meant to make the place feel real and show its character, not to be a document archive.

The block below the form: Prefer the traditional way? Print and fill in a paper application form, Download PDF button

A PDF form below the online form

Below the online form I added a PDF application form that I designed myself. The digital form doesn't have to be the only way. A parent who prefers paper can download the document and fill it in at their own pace.

Result

I show the result honestly.

Today Smyczki has real photos, visible staff, a clear description of its approach and short paths to contact.

The most tangible result is simpler: instead of an empty gallery there's a real picture of the preschool, and a parent can understand faster who they're trusting their child to and what to do next.

Photos in the gallery
0 → 32
Counted in the Web Archive and on the live website.
Core build
1.5–2 weeks
Estimated from memory, without logged hours.
Enrollments and inquiries
no data
The website has no Analytics, so enrollments can't be linked to traffic.

The websites he created for Czarodziejskie Smyczki and SensoBaza are beautiful, modern and clear, and above all they work very well in practice. Parents find the information they need without any trouble, and we have heard very positive feedback about their look and functionality many times.

Ewa Pietras, director of the Czarodziejskie Smyczki preschool (translated from Polish)
Where the data ends

I don't present Search Console data as a result. Clicks from Google went up at the beginning of May 2026, a month before the new website launched, and there's no jump around June 9.

The website also has no Analytics, so traffic can't be linked to enrollments. That's why the most important evidence is the client's own words, not another chart.

Working together

The collaboration started earlier.

Before the paid rebuild of Smyczki, I designed SensoBaza for the same owner. In 2026 I went back to that project, redesigned it completely and moved the static site from Webflow to Astro 7 to cut an unnecessary running cost.

SensoBaza has its own case study because it solves a different problem: I went back to my own work and assessed it anew, built a visual system and planned the migration so as not to risk the existing addresses or the rankings the site had already earned. The new version is already live at the client's address. The two projects share a client and printed materials, but each has its own story.

A corner banner on a green railing: SensoBaza on one side, Czarodziejskie Smyczki on the other, both with a QR code
The shared corner banner of both centers at one address.

Takeaway

What this project taught me.

Smyczki was my first paid project. A year earlier, with the first version of SensoBaza, I went through a similar path, from first ideas and conversations with the client to launch. But that was for free, and expectations are usually lower then. Here I knew from the start that the work was paid, so I had to deal with time pressure and agreements I had to keep.

The technology changed too. I built the first version of SensoBaza in Webflow, and Smyczki in code, using AI coding tools. I deployed it on Cloudflare and connected the form. Those were my first steps with code.


Next case study

TuMedytuj

My own MVP, where the cost of a single meditation changed the pricing before I designed the first screen.

Go to the project

Contact

Let's talk.

I'm looking for my first job as a UX/UI and Product Designer. I'm available right away.