Better Housing Atlas
Building a housing archive and its publication workflow
I turned a personal collection of housing references into a public digital archive, combining research, structured content, development and coordination with architecture studios.
- Project type
- Independent solo project
- Role
- Research · Content structure · External coordination · Product development
- Timeline
- May 2026 onwards
- First release
- 35 studios contacted · Five projects published
- Stack
- SvelteKit · JSON · Vercel
Turning references into a usable archive
My housing references were scattered across articles, PDFs and project pages. I wanted a consistent way to preserve factual information, explain why each project mattered and retain the sources and credits needed to revisit it later.
I defined a repeatable entry structure covering project facts, editorial context, photographs, sources and credits. The structure needed to work across different types of housing without removing what made each project distinctive.
Managing publication dependencies
Publishing involved more than preparing text and images. Entries depended on source verification, image permissions, accurate credits and responses from external contributors.
By the first release, I had contacted 35 architecture studios across Europe. Responses included permissions, corrected credits, additional materials and recommendations for further research.
I organised the work into a repeatable sequence:
- Research
- Draft
- Permission
- Credits
- Publish
This made permissions and attribution part of the publication workflow rather than something to resolve after an entry was ready.
Keeping the first release manageable
The MVP included a homepage, project index, individual entries, structured project data and responsive layouts. Search, filters, maps, public submissions and CMS tooling were deferred.
I used structured JSON to keep the initial implementation manageable while establishing a consistent format for future entries. This prioritised the archive and publication process before expanding the platform.
First-release results
The archive launched with five published projects and a responsive mobile experience. It also established a repeatable approach to researching, documenting, obtaining permissions and publishing new entries.
After launch, further responses brought permissions, corrections and additional material. The figures above describe the first release, rather than the archive’s current total.
The project demonstrates how I connect a digital build with the external coordination and ongoing workflow needed to keep it useful.
Have a role or project in mind?
I’m open to permanent roles, contract projects and part-time engagements. Get in touch to discuss what you’re working on.