Twenty-four sessions across two days and three rooms.

Components won. Pages got worse. Inês walks through twelve production pages and shows where component thinking broke the reading order, the load order and the layout. Then a method for designing the page first and cutting components out of it.

Quivane changed every colour, both typefaces and its radius scale in one release. Sanne shows the token structure that made it a two-week job, the naming rules, the three tokens that broke, and the script that found them.

Cross-document view transitions now work in the browsers that matter. Luca rebuilds a news site's navigation with them: no router, no bundle, one CSS rule per element. He measures the result against the framework version it replaced and shows where it still falls short.

Nuria opens the font files of two banking apps and one newspaper. Which axes made it to production, which were cut for file size, how each team handled fallback, and the one rendering bug that still bites on Android. Bring your own font-face declarations.

Lumbrane's payroll onboarding form had a 41 percent completion rate. Camille rewrote the labels, the errors and the order of questions. Nothing else changed. Completion went to 68 percent. She shows every version, what moved the number and what did not.

Lab scores said Sildrek's sites were fine. Readers said the text jumped. Jonas built a field pipeline that records shift per element, per device class, per country. He shows the pipeline, the ten worst offenders it found, and the fixes that removed 80 percent of the shift.

Lunch is served in the Hall. Vegetarian and vegan options at every station. Dietary needs from your ticket are on a card at the counter.

Three teams, three answers. Sanne runs a system owned by a dedicated team, Marcos moved one to joint product and engineering ownership, Giulia runs one with two designers for nine teams. Forty-five minutes on what each model costs, who pays it, and when to switch. Questions from the room from minute thirty.

Bring a laptop and one animation from your own product. Lena shows her spec format: trigger, duration, easing, reduced-motion fallback, one line each. You write the spec for your animation, swap with a neighbour, and build theirs from the spec alone. Then compare with the original.

Two hundred quotes, one spreadsheet. Théo shows what his studio charged, what it cost, and where the gap came from. Then the three questions he asks on a first call, the number he gives when pushed, and how often that number held.

A newspaper article grid rebuilt live on stage. Elin starts from the print grid, maps it to CSS grid tracks, and resizes from 320 to 1600 pixels without a media query until minute twenty. Then the two breakpoints she could not avoid, and why.

Most of Ostrel's users open the app on a mid-range Android phone on a mobile connection. Harriet shows the onboarding flow before and after a redesign tested only on such phones: fewer screens, no illustration over 20 kilobytes, no step that needs a network round trip to render.

Oliver migrated a retailer's 140-component library from viewport media queries to container queries. He shows the components that got simpler, the four that got harder, the naming scheme for containers, and the 3,000 lines of CSS that were deleted at the end.

Agnieszka builds a prototype to answer a single question, tests it with field engineers on site, and deletes it. She shows six such prototypes from Grenholt, the question each one asked, the answer it gave, and the two that gave the wrong answer because they were too polished.

Bram takes four interfaces from the audience, screen reader on, and navigates them with a keyboard only. Where focus goes, where it gets lost, and why the fix belongs in the design file, not the code. He shows how to mark focus order on a mockup in five minutes.

Two designers, nine product teams. Giulia shows the weekly review that makes the ratio work: what gets reviewed, what ships without review, the checklist engineers use, and the two features that went wrong anyway. Numbers from eighteen months at Corrastel.

Lena's public file has 34 easing curves and a reason for each. She shows the six she uses most, the situations each belongs to, the ones she retired and why. Every example runs live in the browser, side by side with the curve it replaced.

A news site with 23 third-party scripts and no owner for any of them. Luca shows the budget his team set, the loader that enforces it, the scripts that were cut, and the conversation with the marketing team that had to happen first. Load time dropped by 2.1 seconds on mobile.

Lunch is served in the Hall. Vegetarian and vegan options at every station. Dietary needs from your ticket are on a card at the counter.

Marcos has handed over eleven projects as a freelancer and received four as a manager. He shows the handover document he now requires, the one-hour session that goes with it, and what happened to the projects that got neither. Templates in the slides.

A retailer with one phone and no budget can still have consistent photography. Harriet shows the one-page shot list she gives clients, the three lighting rules, and the crop system that makes forty product photos read as one set. Before and after from four shops.

Bring a laptop and a URL you are allowed to break. Jonas runs his audit method on a volunteer's site, then you run it on yours: field data first, lab second, one fix per finding, measured before and after. You leave with a prioritised list and at least one shipped fix.

Kadrel sells in eleven languages. Translating the strings was the easy part. Tiago shows what broke in the layout: buttons in German, dates in Polish, right-to-left navigation, line heights in Japanese. Then the CSS properties that fixed most of it and the component rules that fixed the rest.

Closing talk. Camille collects the empty states, error messages and button labels seen on stage over two days and rewrites them live. One rule per rewrite. Then the list of rules, on one slide, to take home.