Showcase: a website for Devil's Island, my neighbourhood

Showcase: a website for Devil's Island, my neighbourhood

Article

duivelseiland.amsterdam is a website for Duivelseiland ("Devil's Island"), a neighbourhood of about 1,400 residents in Amsterdam-Zuid. It brings together what residents need day to day (when to put out bulky rubbish, what the rules are for renovation noise, which plumber the neighbours recommend) with things that bring people together: activities, a newsletter and the history of the neighbourhood. I built it between September and November 2026 with Claude Code, in Dutch and English, and it runs on free tiers only.

The home page of duivelseiland.amsterdam: an aerial photo of the Roelof Hartplein from the city archive, a welcome text and a map of the neighbourhood

Why does a neighbourhood need its own website?

Information about the neighbourhood is scattered across the WhatsApp group, the municipality's website and a handful of people who have lived here for decades. The WhatsApp group is lively, but a good tip or a question about the bulky rubbish day disappears within a day. The site is meant to be the place where that information stays findable, written for this neighbourhood and not for the whole city.

It is bilingual on purpose. According to CBS, 45% of residents had a Dutch background in 2025, down from 66% in 2013. A neighbourhood site in Dutch only would miss more than half of the neighbourhood.

Where does the name come from?

Duivelseiland isn't an island: there is no water around it. Around 1900, Amsterdammers named this muddy building site after the penal colony off French Guiana where Alfred Dreyfus was imprisoned, innocently. It didn't help that a candle-wax factory on the Hobbemakade made the whole area stink. The history page tells that story with photos from the Amsterdam City Archives and schematic maps of how the neighbourhood grew.

The history page: the headline "An island without water", a photo of the candle-wax factory on the Hobbemakade around 1905 and four key figures

Four schematic maps of the same area in 1896, 1906, 1930 and today: loose wooden houses and the factory, the factory demolished, closed building blocks, and the current neighbourhood

What do residents get out of it?

Waste and bulky rubbish. Bags next to full containers and sofas on the pavement are among the biggest irritations here. The waste page explains the rules and shows where things go wrong, with figures that come live from the City of Amsterdam's open data: container locations, the collection day per address, observations by enforcement officers and public reports. There's a printable instruction card to hang in the hallway.

The "Where it goes wrong" chapter of the waste page: a map with circles where rubbish is most often left next to containers, and a bar chart per street

Noise. The buildings here have shared inner courtyards that act like sound boxes. The noise page sets out when a contractor may work, what applies to parties and what you can do about noise nuisance. Every rule has a source in national or municipal regulations, and the page shows the date it was last checked. Advice the neighbourhood agreed on itself, like "no drilling before 9 am", is labelled as advice, not as law.

The noise page: four key rules at the top and a week chart showing when a company may build

With the note for the neighbours you fill in a letter about your renovation or party, in Dutch, English or both, and print it. Nothing you type leaves your browser: no server, nothing in the URL.

The note generator: a form with the type of note, the language, dates and working hours, and a live preview of the letter

Tradespeople. Plumbers, electricians and carpenters recommended by neighbours, with a clear note that these are not recommendations by the site itself. Neighbours with a neighbourhood pass can suggest one; the editors check it before it goes online.

Activities. A book club, a cooking night, coffee in the parish house: residents organise these themselves. Anyone can submit an idea. Once the editors approve it, the resident becomes an organiser with their own login, sees who signed up and can message participants. Neighbours who want to hear about new ideas get an email the morning after an idea is approved.

The activities page: "Doing things together in the neighbourhood", a button to submit an idea and the weekly neighbourhood coffee

The neighbourhood in numbers. Eight chapters of charts on people, housing, income, mobility, safety, health, facilities, and how the neighbourhood compares with the rest of the Netherlands (43 times as densely populated as the Dutch average). The data comes from CBS (and where needed RDW, police and RIVM), not from sites that repackage it, and every chart shows its source and year. Estimates are labelled as estimates.

The statistics page: 1,381 residents, 860 households, 885 homes, an average property value of €611,000, and a chart of residents' background since 2013

And then there's Mimi, the cat from the pizzeria on the Hobbemakade, who keeps getting reported in the neighbourhood app as a lost kitten. She now has her own page, with a passport that says she's officially not lost.

Mimi's page: "No, she's not lost", with a photo of the grey-and-white cat and her passport

The whole site works on a phone just as well as on a desktop:

Three phone screens side by side: the home page, the waste page and Mimi's page

How do you protect neighbourhood information without user accounts?

Some things shouldn't be on the open internet: the phone numbers of tradespeople who didn't ask for that, WhatsApp links, and news meant only for the neighbourhood. Asking every resident to create an account with a password would be too much of a barrier.

The solution is the neighbourhood pass. You enter your email address and receive a link that works once and for 30 minutes. Click it, then press "Activate", and your device gets a signed cookie that lasts a year. No password, no account. The extra click is there because email scanners open links automatically and would otherwise use up the link.

The tradespeople page: a disclaimer, and a locked block "Phone numbers" where you request a link with your email address

It's important to be honest about what it does and doesn't do. The pass keeps search engines, scrapers and casual visitors out. It does not prove that someone lives in the neighbourhood: anyone with a confirmed email address gets one. You can revoke your pass from the same page, on one device or on all of them at once.

How is it built?

  • One app: Next.js with Payload CMS running inside it. The website and the admin panel are a single codebase and a single deployment.
  • Data: SQLite on Turso, photos in Vercel Blob, hosting on Vercel, Bun as runtime. All on free plans (Vercel Hobby, Turso Free, Blob Free).
  • Roles: admin, editor, author and organiser, each with exactly what they need. An author can write news but not publish it. These rules are enforced on the server in Payload's access functions, not just hidden in the interface.
  • Two languages: interface text through next-intl, content through Payload's localised fields. Editors write in Dutch and press "Translate to English" in the admin. That uses MyMemory, a free translation memory, which turned out to be unreliable for short fragments: "Dit weekend is er een groot feest voor de buurt" ("This weekend there's a big party for the neighbourhood") once came back as "There is a TV, radio and CD-player. One big party! for the neighbourhood." Results below a quality score of 0.7 are therefore discarded, and the field stays empty for a person to fill in.
  • Newsletter: double opt-in, and sending is spread over several days, because Resend's free plan allows 100 emails a day. Bulk email only goes out from production, so a test environment can never accidentally mail the whole neighbourhood.
  • Share previews: a link shared in WhatsApp shows a custom image on every public page, made with Next.js's image generation. The build fails if a public page doesn't have one.

The share preview of Mimi's page as it appears in WhatsApp: a photo with an "officially not lost" stamp and her passport details

What did Claude Code do?

I built the site with Claude Code. From the first commit on 10 September to 9 November 2026, the repository has 234 commits on 26 days, and 55 merged pull requests. 120 of the 162 commits that aren't merges were written together with Claude (own count from the repository's history on GitHub).

What made that work:

  • A written specification. PROJECT.md describes the roles, the permission table, the stack and what was deliberately left out. Claude reads it at the start of every session, so decisions don't have to be explained again.
  • Working agreements in CLAUDE.md. For example: only Bun, permissions enforced in access functions, every public page needs a share image. The share-image rule is also checked by a script in the build.
  • Briefs before code. Larger parts, like the history page and the statistics, started with a design brief describing what the page should tell and where the data comes from.
  • Parallel work in worktrees. Each feature gets its own branch and checkout, so several sessions can run side by side without getting in each other's way.

I decided what the site does and for whom, gathered the sources, and tested and reviewed everything. Claude wrote most of the code.

Have a look

The site is live at duivelseiland.amsterdam, and the code is public on GitHub. Want something like this for your own neighbourhood, club or organisation? Get in touch.

More articles