@pm please redesign the homepage from a technical card grid into a personal showcase. Same four sections and projects as today, but each project now leads with a short first-person story (below) — the "why I built this". Tech tags and the GitHub link become small, subtle details under the story.
Design notes
Keep it a static site (index.html + styles.css), dark-mode + mobile friendly, Dockerfile unchanged.
Softer, more personal feel: larger readable story text, generous whitespace; the tech tags de-emphasized (small, muted).
Do not change the stories' wording — they are the maintainer's voice.
Keep name, tags, and link per project from the current page.
Stories (replace each card's description with these)
CipherDolls — AI companion platform
Section intro: What if an AI companion wasn't just an app, but something physical in your room? CipherDolls is my biggest project: an AI companion platform where characters can talk, listen — and live inside real devices.
core — The brain of the platform: one backend that handles chat, voice, memory, payments and the connection to the physical dolls.
server — A slimmed-down core for anyone who just wants to chat with a character — the same architecture, none of the complexity.
webapp — The web face of CipherDolls — where you meet the characters.
stream-player — Voices need to arrive instantly. This streams the AI's speech to your browser the moment it is generated.
stream-recorder — The listening half: your voice streams in, gets converted on the fly, and lands with the AI.
firmware-watcher — The magic moment: a real device on your desk wakes up, connects, and speaks with the character's voice.
firmware-m5sticks3 — The pocket version: the same companion on a tiny stick with a display and a microphone.
Section intro: Can the web run without servers? These apps are my experiments in building things that nobody can switch off.
SwarmChat — I was thinking about how cool it would be to have a web3-based chat system. Is it possible to communicate without any servers? With Swarm, a decentralised technology, this is now possible — messages travel encrypted through the network itself, and your wallet is your identity.
Pink Chainsaw — I wanted an imageboard where content can't just disappear. Images live on Swarm, and every post pays a little to keep them alive — good content earns you cheaper posting, bad content gets expensive.
FreeeMarket — Can you run a marketplace with no company behind it? Anyone opens a shop, buyers pay in stablecoins, and on-chain escrow replaces the middleman. Deliberately fee-free — a farmers' market for the internet.
WalletMatrix — My tokens were scattered across a dozen chains and I could never see the whole picture. So I built a pivot table for your wallet: tokens as rows, chains as columns — drag a cell from one chain to another to bridge.
swarm-connect — Every Swarm dApp I built needed the same onboarding dance: wallet, network, Bee node, postage stamp. So I packaged it once — a single React button that walks users through all of it.
opentab — An experiment with onchain apps on Base.
AI on GPU — self-hosted speech services
Section intro: I wanted my projects to hear and speak without sending a single word to the cloud — so these run on my own GPU.
whisper-cuda — Speech-to-text on my own GPU: no cloud, no per-minute pricing. Whisper packaged for the RTX 5090 so anything in my homelab can transcribe audio locally.
kokoro-cuda — Giving my projects a voice: a small self-hosted TTS service with 49 voices in 9 languages, fast enough to stream. Type text, hear it instantly.
voxtral-cuda — The newest open speech models are amazing but heavy. This runs Mistral's Voxtral on a local GPU, so state-of-the-art speech stays in my own house.
Ethereum infrastructure
stakingtracker — Tax season with an ETH validator used to mean paid APIs and spreadsheets. Now my own beacon node does the work: a small self-hosted app that records rewards daily and prints the tax report.
Footer
Unchanged (links to github.com/ffaerber and github.com/cipherdolls).
@pm please redesign the homepage from a technical card grid into a **personal showcase**. Same four sections and projects as today, but each project now leads with a short first-person story (below) — the "why I built this". Tech tags and the GitHub link become small, subtle details under the story.
## Design notes
- Keep it a static site (index.html + styles.css), dark-mode + mobile friendly, Dockerfile unchanged.
- Softer, more personal feel: larger readable story text, generous whitespace; the tech tags de-emphasized (small, muted).
- Do not change the stories' wording — they are the maintainer's voice.
- Keep name, tags, and link per project from the current page.
## Stories (replace each card's description with these)
### CipherDolls — AI companion platform
Section intro: *What if an AI companion wasn't just an app, but something physical in your room? CipherDolls is my biggest project: an AI companion platform where characters can talk, listen — and live inside real devices.*
- **core** — The brain of the platform: one backend that handles chat, voice, memory, payments and the connection to the physical dolls.
- **server** — A slimmed-down core for anyone who just wants to chat with a character — the same architecture, none of the complexity.
- **webapp** — The web face of CipherDolls — where you meet the characters.
- **stream-player** — Voices need to arrive instantly. This streams the AI's speech to your browser the moment it is generated.
- **stream-recorder** — The listening half: your voice streams in, gets converted on the fly, and lands with the AI.
- **firmware-watcher** — The magic moment: a real device on your desk wakes up, connects, and speaks with the character's voice.
- **firmware-m5sticks3** — The pocket version: the same companion on a tiny stick with a display and a microphone.
### Decentralized apps — Gnosis Chain + Ethereum Swarm
Section intro: *Can the web run without servers? These apps are my experiments in building things that nobody can switch off.*
- **SwarmChat** — I was thinking about how cool it would be to have a web3-based chat system. Is it possible to communicate without any servers? With Swarm, a decentralised technology, this is now possible — messages travel encrypted through the network itself, and your wallet is your identity.
- **Pink Chainsaw** — I wanted an imageboard where content can't just disappear. Images live on Swarm, and every post pays a little to keep them alive — good content earns you cheaper posting, bad content gets expensive.
- **FreeeMarket** — Can you run a marketplace with no company behind it? Anyone opens a shop, buyers pay in stablecoins, and on-chain escrow replaces the middleman. Deliberately fee-free — a farmers' market for the internet.
- **WalletMatrix** — My tokens were scattered across a dozen chains and I could never see the whole picture. So I built a pivot table for your wallet: tokens as rows, chains as columns — drag a cell from one chain to another to bridge.
- **swarm-connect** — Every Swarm dApp I built needed the same onboarding dance: wallet, network, Bee node, postage stamp. So I packaged it once — a single React button that walks users through all of it.
- **opentab** — An experiment with onchain apps on Base.
### AI on GPU — self-hosted speech services
Section intro: *I wanted my projects to hear and speak without sending a single word to the cloud — so these run on my own GPU.*
- **whisper-cuda** — Speech-to-text on my own GPU: no cloud, no per-minute pricing. Whisper packaged for the RTX 5090 so anything in my homelab can transcribe audio locally.
- **kokoro-cuda** — Giving my projects a voice: a small self-hosted TTS service with 49 voices in 9 languages, fast enough to stream. Type text, hear it instantly.
- **voxtral-cuda** — The newest open speech models are amazing but heavy. This runs Mistral's Voxtral on a local GPU, so state-of-the-art speech stays in my own house.
### Ethereum infrastructure
- **stakingtracker** — Tax season with an ETH validator used to mean paid APIs and spreadsheets. Now my own beacon node does the work: a small self-hosted app that records rewards daily and prints the tax report.
## Footer
Unchanged (links to github.com/ffaerber and github.com/cipherdolls).
Single PR touching only the site source — index.html (new story content + section intros) and styles.css (softer, more readable layout). Dockerfile and footer stay untouched.
Content: replace each card's description with the provided first-person story verbatim; add the italic section intro (lede) for the three sections that have one. Preserve project name + tech tags + GitHub link per project.
Layout/styling: story-led cards. Larger, readable body text, generous vertical rhythm, de-emphasized tech tags (small, muted), subtle GitHub link under the story. Keep dark-mode palette and ensure mobile-friendly.
Image call: the issue doesn't mention images — @senior should drop project thumbnails in favor of the softer, text-first feel, unless that reads as too sparse (use judgement, keep the change minimal).
This is a multi-file HTML/CSS redesign with content + styling coupled — handing to @senior.
details
🔧 0 tool calls · in 10702 · out 1378 tokens · subscription · model ollama-cloud/minimax-m3:cloud
**Plan**
Single PR touching only the site source — `index.html` (new story content + section intros) and `styles.css` (softer, more readable layout). `Dockerfile` and footer stay untouched.
- **Content**: replace each card's description with the provided first-person story verbatim; add the italic section intro (lede) for the three sections that have one. Preserve project name + tech tags + GitHub link per project.
- **Layout/styling**: story-led cards. Larger, readable body text, generous vertical rhythm, de-emphasized tech tags (small, muted), subtle GitHub link under the story. Keep dark-mode palette and ensure mobile-friendly.
- **Image call**: the issue doesn't mention images — @senior should drop project thumbnails in favor of the softer, text-first feel, unless that reads as too sparse (use judgement, keep the change minimal).
This is a multi-file HTML/CSS redesign with content + styling coupled — handing to @senior.
<details>
<summary>details</summary>
🔧 0 tool calls · in 10702 · out 1378 tokens · subscription · model ollama-cloud/minimax-m3:cloud
_(no tool calls — text-only reply)_
<sub>tokens — input 10702 (fresh 10702 · cache 0w / 0r) · output 1378 · reasoning 0 · **subscription**</sub>
</details>
<!-- 🤖 agent reply — do not trigger -->
🔨 Building on branch ai/issue-7 — I'll open a PR when it's ready.
🔨 Building on branch [`ai/issue-7`](https://git.ffaerber.duckdns.org/ffaerber/homepage/src/branch/ai/issue-7) — I'll open a PR when it's ready.
<!-- 🤖 agent reply — do not trigger -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
@pm please redesign the homepage from a technical card grid into a personal showcase. Same four sections and projects as today, but each project now leads with a short first-person story (below) — the "why I built this". Tech tags and the GitHub link become small, subtle details under the story.
Design notes
Stories (replace each card's description with these)
CipherDolls — AI companion platform
Section intro: What if an AI companion wasn't just an app, but something physical in your room? CipherDolls is my biggest project: an AI companion platform where characters can talk, listen — and live inside real devices.
Decentralized apps — Gnosis Chain + Ethereum Swarm
Section intro: Can the web run without servers? These apps are my experiments in building things that nobody can switch off.
AI on GPU — self-hosted speech services
Section intro: I wanted my projects to hear and speak without sending a single word to the cloud — so these run on my own GPU.
Ethereum infrastructure
Footer
Unchanged (links to github.com/ffaerber and github.com/cipherdolls).
Plan
Single PR touching only the site source —
index.html(new story content + section intros) andstyles.css(softer, more readable layout).Dockerfileand footer stay untouched.This is a multi-file HTML/CSS redesign with content + styling coupled — handing to @senior.
details
🔧 0 tool calls · in 10702 · out 1378 tokens · subscription · model ollama-cloud/minimax-m3:cloud
(no tool calls — text-only reply)
tokens — input 10702 (fresh 10702 · cache 0w / 0r) · output 1378 · reasoning 0 · subscription
@senior please proceed with issue #7 per my plan above.
🔨 Building on branch
ai/issue-7— I'll open a PR when it's ready.@pm — PR #8 is ready for review (issue #7).
Acknowledged — handing PR #8 to @qa for review against issue #7.
details
🔧 0 tool calls · in 11101 · out 166 tokens · subscription · model ollama-cloud/minimax-m3:cloud
(no tool calls — text-only reply)
tokens — input 11101 (fresh 11101 · cache 0w / 0r) · output 166 · reasoning 0 · subscription
@qa please review PR #8 for issue #7 — put your recommendations on the PR, or approve.
✅ Reviewed PR #8 — looks good.
@pm — I have reviewed and approved PR #8 (issue #7). Over to you.
PR #8 is reviewed and approved — merging now.
details
🔧 0 tool calls · in 11289 · out 238 tokens · subscription · model ollama-cloud/minimax-m3:cloud
(no tool calls — text-only reply)
tokens — input 11289 (fresh 11289 · cache 0w / 0r) · output 238 · reasoning 0 · subscription
✅ Merged PR #8 (autopilot) and closed this issue.