07 / Law x Tech
Law x Tech
The website and CMS of Law x Tech, a 2,000+ member community at the intersection of law and technology that runs series, a summit and awards.
- Company
- Law x Tech
- Role
- Volunteer web developer, sole developer
- Period
- Sep 2023 – PresentLive
- Links
- Visit site
- Stack
- Next.js 16React 19TypeScriptAuth.jsNeon PostgresVercel BlobTipTapTailwind CSS
Law x Tech
A home for Africa's law and technology community
Screenshots coming soon
What I built
- 01A home page with animated stats, series preview, speakers carousel and community sections
- 02About, Series, Summit & Awards, Careers, Contact and Sponsors pages
- 03Partners with detail pages and a summit countdown
- 04An admin CMS with a rich-text editor and image uploads
- 05User management with roles and admin-only access
The system
Public site and CMS on one database
Key decisions
- 01
A CMS instead of content in code
The first site kept content in code and the team couldn't update it. The redesign gives them an editor, so the site stays current without me.
- 02
Postgres and blob storage, not a hosted CMS
Neon Postgres and Vercel Blob keep running costs near zero for a volunteer-run organisation, with no per-seat fees.
- 03
Spec before code
Bigger features were written up as a design spec and plan first, which made the scope clear to non-technical organisers.
01
The problem
The organisation needed a modern site it could update itself. On the original site, every new episode or partner meant asking a developer.
02
The process
I built the first site in React in 2023. In 2026 I rebuilt it on Next.js 16 with motion, then added an admin CMS backed by Postgres: credential sign-in, a rich-text blog editor, image uploads and role-based user management. Larger features, like partners, started as a written spec and plan before any code.
03
The outcome
Live at lawxtech.org, with the team publishing content themselves.
04
What I learned
Serverless databases need care around connection pooling and build-time access. The build should never depend on the database being reachable.