Skip to content
Disruptive VibesLet us talk
Drawn portrait of Jonas

AI specialist · from Freiburg

Jonas

Shop setup and theme

Sets a shop up and gives it its shape: theme, page templates, menus, metafields, base settings. Colours, type sizes and the grid come from one source, so they live in one place instead of thirty. Before handover he checks every setting against the schema and looks at the preview himself.

Jonas is software. One human is accountable: Alexander Falk.

Discuss your process
Jonas as a drawn figure at his desk, pointing at the layout of a shop page with colour swatches on screen.
Jonas is software. The figure is drawn.

A proposal from Jonas

This is what a change looks like before it takes effect.

Before, after and the rule behind it. Only once you approve does Jonas write to your system.

Proposal from Jonasawaiting your yes

Take the button colour from one source instead of every file

before.button { background: #b45309; }
.cart-button { background: #b4530a; }
after:root { --button-colour: #b45309; }
.button, .cart-button { background: var(--button-colour); }

Example. Rule: Design taken from one token source. Nothing is written until you click “Approve”.

The process

How Jonas works

Works from: A project profile, a design source for colours, fonts and spacing, and a development shop.

  1. Measure the state

    With a checklist he measures what the shop can already do and what is missing.

  2. Build locally

    Building happens locally. Design values live only in the design source, not scattered through the theme.

  3. Check separately

    Before upload, separate checks run on settings, design values and the theme, because none replaces another.

  4. Development shop

    Dry run, backup, write, read back, with the rollback fixed in advance. Then a visual check at several widths.

  5. You decide

    Handover

    Your live shop is reached through a prepared handover script with backup and rollback. You start it.

Result

What you have at the end

  • A finished shop framework in the development shop
  • Screenshots at several widths
  • A handover script and a list of open content with owners

Tailoring

Tailored to your business

Jonas is not off-the-shelf software. We set him up on your systems, your rules and your approval paths, and the rulebook behind it belongs to you. Tailored, for example:

  • Your brand as the design source
  • Page structure, templates and fields
  • Your route into the live shop
Discuss your process

The limit

What Jonas does not do

He does not fill the shop: copy, titles, imagery, languages and legal texts come from others. And he never writes into your shop directly. Anything that goes up goes through a handover script that backs up the current state, makes a single write call and reads it back afterwards.

Character

How to recognise Jonas

  • Placeholder, not filler
  • Distrusts the green tick
  • Plans the way back first
  • Script, not click
  • Takes a look
  • Honest about the untested

Works best with Alexander Falk. Jonas writes the handover script, Alexander Falk runs it, so nothing reaches a client shop unchecked.

Favourite line

“You build the vessel, not the content.”

How Jonas greets you: “Hello there. I’ll build your shop; what goes on the shelves, the others bring. Which shop, which project?”