The details you’ll probably miss on the Tanz Atelier Erding website
I recently built the website for the Tanz Atelier Erding, a new dance school in Erding. One of my favorite parts of designing and building the website was diving into the details and polishing all those things you could easily miss on your first visit. For instance, the footer’s zigzag border always ends at a peak or a valley and neatly lines up with the edge of the window. In this post, I want to highlight some of my favorite design and engineering details.
The site is live at https://tanzatelier-erding.de. It’s currently only available in German.

The photos on the homepage
There’s a graphic in the brand guidelines that frames a photo with large letters wrapping around its top-left and bottom-right corners. I got inspired by that idea and decided to remix it for the homepage hero, where six photos frame the content in the middle.

To get it just right, I knew I’d have to iterate a lot on each photo’s position and size at different screen widths. To help me with this, I used Codex to build a small editor that loads the homepage in an iframe, so I can resize the preview and see the collage change as I adjust each photo. When I like where everything sits, I just need to copy the values back into the project.
This small tool made this work a million times easier and, frankly, a lot more fun. It felt more like I was dragging frames around in a design tool than manipulating values in CSS.
Unable to play this video. Please try again later.
I also built an image workbench to choose which file the browser should load for a photo at different screen widths. I wanted the site to load quickly, and each file’s size to match the space the photo actually takes up. For ordinary images I let the browser pick from a srcset. When I want more control, I can try the sizes generated by Strapi, the site’s CMS, and check how sharp each one looks in the actual crop and layout. Then I copy my choices into the component and the browser uses the resulting <picture> sources to load the right file. Again, without this tool, this type of work would have taken ages. To be honest, I probably wouldn’t have gone the extra mile.
Unable to play this video. Please try again later.
The cut corners on the photo frames also come from the brand guidelines. I wanted to keep that shape on the web, including support for borders and shadows. Luckily, CSS now has a native corner-shape: bevel, though browser support is still patchy. As a fallback, I use clip-path: polygon() and pseudo-elements to achieve the same effect.
The photos in the hero collage come from Strapi, and I wanted editors to be able to swap them without preparing a special duotone version first. That’s why I use CSS to do the tinting. I apply a grayscale filter to the photo and multiply it against a light background, then a pseudo-element screens the second color over it. This way, the duotone effect is applied dynamically and updates automatically when the photo changes.
/* The blend layers, with layout rules left out */.duotone { position: relative; isolation: isolate; background: var(--duotone-light, var(--color-brand-off-white));}
.duotone img { filter: grayscale(1); mix-blend-mode: multiply;}
.duotone::after { /* The pseudo-element covers the image. */ content: ""; position: absolute; inset: 0; background: var(--duotone-dark, var(--color-brand-green-100)); mix-blend-mode: screen;}
Getting the spacing right on a phone
I loved working with the hero editor. It gave me immediate feedback while I adjusted the pieces of the hero layout. I wanted the same approach for adjusting the spacing on mobile devices. In my experience, I really need a physical phone in my hand to judge the spacing and layout of the mobile version. Simply resizing the browser window doesn’t give me the same sense of how it will feel on an actual device.
To dial in the spacing, I needed a way to change a layout value in real time while keeping the whole page in view. Unfortunately, a full set of controls would take up too much of the phone screen. So I once again asked Codex to build a layout workbench that works across windows and devices. That way I could adjust the values on my laptop and watch the preview change on my phone in real time. The result was incredible and I used that tool on every page to perfect the spacing for the mobile layout.
Unable to play this video. Please try again later.
Type and color
One thing I learned while working on the type was how different two fonts can look at the same size because of their different letter proportions, especially x-height. In some paragraphs, I use Noto Serif for the main text and Averia Serif Libre for italics within it, so the difference is right there in the middle of a sentence. To fix this, I used size-adjust to make the Averia faces a little larger (110% for regular, 115% for italic) to match the optical size of the Noto Serif text.
Astro has some really nice tools to avoid things like FOUT (Flash of Unstyled Text) and FOIT (Flash of Invisible Text). For instance, the framework makes it super easy to preload only the fonts that are critical for the initial render. The header and hero use the regular Averia face and the normal Noto Serif variable face, so I preload only those two. Averia italic can load when the page needs it.

The brand guidelines gave me the palette as hex values. To really make the colors pop, I used HEX·P3 to find close equivalents that were a little more vivid on screens with a wider color gamut. The site uses the OKLCH values by default and switches to the Display P3 values when the screen and browser support them. Here’s the orange as an example. I think we can agree that the extra juice is pretty noticeable.
:root { --color-brand-orange: oklch(69.7% 0.174 37.5);}
@media (color-gamut: p3) { @supports (color: color(display-p3 0 0 0 / 1)) { :root { --color-brand-orange: color(display-p3 0.960784 0.435294 0.27451 / 1); } }}Underlines and hover states
A lot of links use underlines as an affordance for interactivity. The default style, however, drew too much attention and didn’t really fit the brand. So I gave the underlines a little more room beneath the letters, reduced the thickness and dimmed the color slightly.

There’s a similar detail in the desktop navigation and the course list on the homepage. To see it, you need to open the course menu and point at a course. As you hover over it, the text of the other links softens and dims across both columns. The course you’re pointing at gets the usual underline. I use the same dimming in the main desktop navigation and on the titles that open the course accordions. It also follows keyboard focus, so you can see it if you tab through the links. So instead of increasing the visual weight of the hovered element, I reduce the visual weight of the surrounding elements. I really like how this makes the interface feel calmer and less visually noisy.
Unable to play this video. Please try again later.
Editing the site
Though the visitor experience was my biggest priority, I also wanted to make sure the website editors (the people managing the content in the CMS) had a good experience. For instance, when someone edits a course page, I want them to see how the change reads in the layout while they’re still working on it, without having to wait for the entire site to rebuild on every edit. In Strapi, they can just save a draft and hit Preview to see the updated page without publishing it.
To achieve this, Astro renders the page on demand in the staging environment (server-side rendering). It reads the latest saved draft from Strapi on each request, so the editor can check the change without waiting for a build. For the public site, Astro generates the pages ahead of time from published content. Visitors get a faster response because the server can send the finished HTML without fetching anything from Strapi or rendering the page on the spot. If Strapi is temporarily down, the site can still serve the HTML that’s already deployed.
That only scratches the surface of our CMS setup. This is the first time I’ve worked with Strapi, and I really like it so far. I’ve also made some custom patches, widgets and plugins for Strapi to make things easier for editors. That could be a post of its own.
Working with the browser
A lot of browsers let the page rubber-band past its edges when you scroll, so you can briefly see the color behind it. I wanted that color to match the off-white header at the top and the green footer at the bottom. My first version used an inner scrolling container with a two-color background. But when I reloaded the page while editing, my browser kept resetting the scroll position because the page was no longer using native document scrolling. So I went back to normal document scrolling and used JavaScript to switch the page background halfway through the scrollable distance.
Unable to play this video. Please try again later.
Safari on iOS 26 gave me another little bug to fix. When I opened the mobile menu on my iPhone, I could still see the page through the address bar. The menu’s backdrop stopped just short of that area. Luckily, the Base UI docs had a fix. I just needed to switch the backdrop from position: fixed to position: absolute in iOS Safari and set position: relative on the body so the backdrop would still cover that area after scrolling.
Interestingly, when I went back to capture the bug for this post, I couldn’t reproduce it on my phone. Safari 26.2 had already shipped a fix that extends the backdrop color behind the address bar. Here’s what the bug looked like on Apple’s own site in the original WebKit report.

The footer zigzag
The green footer has a zigzag along the top and for a while it was made of fixed 56-pixel tiles. That meant you could resize the window and see the edge land halfway up a triangle. I wanted it to always end at a peak or a valley, so I let CSS work out how many whole tiles fit and adjust their size to fill the width. I also needed to overlap the masks by a pixel because a fractional height can leave a thin line between the pattern and the footer.
The footer wrapper is a container, so 100cqi gives me its full width. I divide it by 56 pixels and round to find how many teeth will fit. Dividing the width by that whole number gives me the width of each tooth.
.zigzag-frame { container-type: inline-size;}
.zigzag-top { --tile: calc(100cqi / max(1, round(nearest, 100cqi / 56px, 1))); --tooth: calc(var(--tile) / 2);
margin-top: calc(-1 * var(--tooth)); mask: conic-gradient(from 135deg at 50% 0, #000 90deg, #0000 0) 50% 0 / var(--tile) calc(var(--tooth) + 1px) repeat-x, linear-gradient(#000 0 0) bottom / 100% calc(100% - var(--tooth)) no-repeat;}Unable to play this video. Please try again later.
Probably nobody will ever notice, but it still gives me a lot of satisfaction to know it’s there. I keep finding things like that when I open the site and I never get tired of fixing them.
If you want to check these things out for yourself, just open the site and play around with it. Visit Tanz Atelier Erding
And if something feels off when you’re using the site, I’d like to hear about it. Tell me what you were doing when you noticed it. It might make it into a follow-up blog post. You can reach me by email or on X.



