Log — What we build here step by step with AI

Here we record every building step in plain language: what changed, why it matters and what you can learn from it. The site calculates the numbers at the top itself on every build. The setup in detail is described in Thought #451.

As of November 9, 2026

Total pages1,066 static HTML pages
Total wordsGerman repository · 450 thoughts · 88,011 words (≈ 352 book pages)Across German, English, Russian and Ukrainian: 218,789 words (≈ 875 book pages)
Quality checks before every deploy31 test suites · 15,022 automated individual checks

How we work together

Torsten speaks his thoughts and decides on every step. Gemini is the sparring partner and turns them into a clear work order as a file. Claude Code reviews as a critical editor, builds the pages on a Chromebook with Linux, runs all tests and publishes via Cloudflare Pages after Torsten's “go”.

Entries

  1. Raw files stay private

    A text file of collected discussion material had accidentally gone online. It is offline again, and from now on the site never publishes loose text or document files from its content folders – a test keeps watch.

    What you can learn from it: What you collect only for thinking belongs in a private folder – and a fixed rule is safer than being careful.

    At the time: 1,066 pages · 218,789 words · 15,022 checks in 31 test suites

  2. This log is born

    From now on every release leaves a trace here: the date, what changed and the real numbers – pages, words and green checks. The site calculates the numbers at the top itself on every build.

    What you can learn from it: Documenting your steps openly teaches you the most – and others can rebuild it.

    At the time: 1,066 pages · 218,789 words · 15,013 checks in 31 test suites

  3. Google-style search results

    Search now shows the address, the title and the highlighted passage for every result – light, clear and, on phones, in its own row with a clearly visible “Search” button.

    What you can learn from it: Browsers keep stylesheets for hours – that's why every new version now carries its own version number.

    At the time: 1,064 pages · 14,939 checks in 30 test suites

  4. Search finds every text, Thought #451

    Torsten's phone test with “Cornelia Ketscher” revealed a gap: the big search on the thoughts overview only knew thoughts. Now it also finds matches on other pages and shows the matching passage right away. Thought #451 “Who Is Speaking Here” is published too.

    What you can learn from it: Real tests on your own phone find what automated tests miss – together they make a site strong.

    At the time: 1,064 pages · 14,914 checks in 30 test suites

  5. Full-text search on every page, Thought #450, /uk/thoughts/

    Every page now has a search at the top that finds exact text passages across the whole site and jumps straight to the highlighted sentence – built in-house, in four languages. Thought #450 and an overview of the Ukrainian thoughts are published too.

    What you can learn from it: Your own search can be built in a day today – it used to mean embedding Google search and putting up with ads.

    At the time: 1,060 pages · 14,778 checks in 29 test suites

  6. “read prompt”: handing over tasks with one command

    Long work orders from Gemini land as a file in the Downloads folder. In the terminal, “read prompt” is now enough: the newest file is loaded, shown with its name and time, and the previous task is archived.

    What you can learn from it: Small tools against friction save nerves every day – here: no more pasting long texts into the terminal.

    At the time: 1,055 pages · 14,624 checks in 27 test suites

  7. Safe full rebuild with a site guard

    A rebuild of the whole site now runs first in a sealed-off test environment. A site guard then compares every page with the current version – on the first run all 1,047 pages were identical. Thoughts #448 and #449 are published too.

    What you can learn from it: Compare first, then apply: that way a change only alters what is really intended.

    At the time: 1,047 pages

  8. SafeSpace in four languages, Ukrainian joins

    The SafeSpace section is built in German, English, Russian and Ukrainian. All thoughts get fixed themes, and the About page is redesigned.

    What you can learn from it: A new language is no longer a big project for an AI team – what matters is that a human checks the tone.

  9. Voice notes become thoughts, Events rebuilt

    Many short thoughts grow from Torsten's spoken notes into full texts in German, English and Russian. The Events page gets dates, photos and a corner for joining in.

    What you can learn from it: Your own voice is the most valuable raw material: the AI arranges, but it invents nothing.

  10. Counter for thoughts, words and book pages

    The repository now shows live how many thoughts, words and book pages there are. Very short texts stay out of Google's index for now, and every page carries its real publication and update date.

    What you can learn from it: Numbers that calculate themselves stay honest – nobody has to update them by hand.

  11. Working in the Linux terminal, automated tests and backups

    From now on Claude Code works directly in the Chromebook's Linux terminal. Automated tests check the pages before every release, and a backup copy is made before bigger changes.

    What you can learn from it: Tests are like a net under the high wire: you dare more because a mistake shows up at once.

  12. Moving from Webflow to Cloudflare Pages

    The site leaves the Webflow builder and has since run as pure static pages on Cloudflare Pages – no database, no builder platform fee, fully in our own hands.

    What you can learn from it: If you own your pages as plain HTML files, you can move at any time, and every tool – including an AI – can work with them.

Two Areas of UNO.TEAM

UNO.TEAM now has several areas where we're active. One is the SafeSpace area with the walk through the neighborhood – linked to it are the Scott Peck circles and the neighborhood reporting.

Another area is coaching for independence, for freedom on the web slash AI: How do I master AI? How do I use AI so that people – including people who may still be Jobcenter clients right now – can use AI to create a new space for themselves, a new dimension, a new medium, a new instrument, to express themselves and to turn their creativity into monetary value as well? Or, put very simply: How can I use AI to go self-employed, to be independent and to build myself an alternative to a job?

Who Is Speaking Here

And it has to be visible – that's why I'm starting with it right now – who is speaking here: What gives me the confidence that I have this expertise? We can put together a clear profile, and among other things it will say that I built a website with a team – a team I found myself, an international team. I built several websites, made many attempts, went through many versions and stages, and the highest stage was a website I sold for what would be $300,000 today, adjusted for inflation.

Time for Money – or a Website That Works Around the Clock

And for me it was always important to achieve two things: I create something that works without me, that is bigger than me, that also generates an income for me without my having to work at the same time – so time-shifted, a passive income, so to speak. Although "passive" of course needs defining, because this isn't about passivity at all – it's about an alternative to "time for money". Because even now, for most solopreneurs, they only earn money when they work – fees are time-based. When a coach or a freelancer can't work, she earns no money, no matter how high her rate is. But when I build a website, that website generates an income around the clock. And maybe the website only earns 10 euros an hour – but it does that 24 hours a day and 365 days a year, nonstop, wherever I am, however I'm doing, and regardless of how much extra time I put into the website on top. That has been with me – this process has been with me since 1998.

No CMS, No Wix, No Schmix

And now, in 2026 / 2027, we've made it: We've reached a point where solopreneurs no longer need an agency, where they no longer need a CMS either. They don't need a content management system, they don't need Wix, no Schmix, no Squarespace, whatever they're all called, no Webflow either – they don't need any of that bells-and-whistles stuff anymore. I'm happy to show them, step by step, how to free themselves completely from others and how, for a very small amount of money, they can have complete freedom and access to the best developer teams in the world – namely AI developer teams. They're already up and running. I've been working like this with my current setup since the end of October / November, in the combination Claude Code, Gemini, Cloudflare, Linux / Chromebook. And over the next two, three years there will be enormous gains again in simplicity and in power. And now is the time to break free from these dependencies. And I'm glad to walk alongside them by sharing my experience here. I'll start doing that right now, openly and accessible to everyone. And if anyone also has specific questions, they're very welcome to get in touch with me – I will answer every question.

Why Builders Like Webflow Hold You Tight

Visual builders like Webflow are comfortable as long as you stay inside them. The designer only works one way: once you export the code, you lose the connection to the designer and the CMS – after that, the site can no longer be maintained there. On top of that come heavy bundled scripts, deeply nested containers and platform fees that keep coming every month for as long as the site is online. An AI developer team made up of a Chromebook with Linux, Gemini, Claude Code and Cloudflare Pages writes lean HTML of your own instead, and it belongs entirely to you. Compared with an agency, it costs only a fraction. A few basics in the Linux terminal are part of it – and that's exactly where I'm glad to walk alongside you, step by step.

Our Setup, Step by Step (as of November 9, 2026)

This list keeps growing: it's our living setup documentation, and every new building block gets added here. Every single step, with its date and numbers, is in the Log.

  1. Voice first. Capture thoughts on the go as voice recordings, so the real voice leads the whole process.
  2. Structure in dialogue. Reflect on observations with Gemini, check facts against sources and write a clear work order.
  3. One-command handover. The task file lands in the Chromebook's Downloads folder, and in the Linux terminal “read prompt” is enough. A small loader fetches the newest file, shows its name and time so an old task stands out at once, and archives every earlier task.
  4. Check first, then build. Claude Code reads every draft first as a critical editor – voice, privacy, facts and sources, language tier – and I decide on every point before anything is built.
  5. A Zettelkasten of static pages in four languages. More than 1,060 pages in German, English, Russian and Ukrainian, with theme paths, reading times, related thoughts and structured data for search engines.
  6. Full-text search across the whole site. A search index that only loads on the first keystroke finds exact text passages on every page – in the header of each page and in the big search on the overview pages – and jumps straight to the highlighted sentence.
  7. Automatic guardians. 31 test suites with more than 15,000 individual checks verify links, translations, layout, privacy boundaries and the invitational language of our offer pages. Before bigger changes, a backup copy is made.
  8. Publishing over a global network – and an open invitation. Pure static HTML goes online via Cloudflare Pages. And anyone who wants to make themselves independent this way can ask me any question.