Event website with its own admin system
Iwade Rock
The website for Iwade Rock, a community music event held every two years that raises money for charity, built for the organiser with an admin dashboard so they can run it themselves between events.
How it fits together
- Organiser
- Admin dashboard
- Photo uploads
- API
- Serverless Node API
- Storage
- Table Storage
- Blob Storage
- Visitors
- Public site
- Facebook news feed
The challenge
The organiser of Iwade Rock needed more than a static page. Line-ups, tickets, sponsors, food vendors, news and photos all change in the run-up to each event, and the organiser needed to keep them up to date without calling a developer, on hosting that costs little and needs no server looking after.
What was built
- A mobile-first public site with a countdown to the event, the supported charities, an artist line-up with expandable band cards and videos, food and attractions, sponsors, and ticket tiers that show when a ticket is featured, free or sold out.
- A photo gallery with a lightbox and lazy-loaded images, plus a carousel of memories from past events.
- A news ticker fed from the event’s Facebook page, with a manual fallback.
- An admin dashboard where the organiser manages bands, sponsors, vendors, tickets, news, FAQs, the team, event details and gallery uploads.
- Visitor analytics built into the dashboard and stored by the site itself, rather than handed to a third-party tracker.
- Seasonal themes that switch on by date, which the organiser can override.
Technical highlights
- 01
Run by the organiser
Each type of content is defined by configuration and managed through one shared admin component, so adding a new kind of content doesn’t mean building a new screen.
- 02
Serverless on Azure
The site is hosted on Azure Static Web Apps, with a small Node API, content in Azure Table Storage and images in Blob Storage. There is no server to patch, and running costs stay low between events.
- 03
Safe changes
Pushes to the main branch deploy to production, and the development branch deploys to a separate staging site. Pull requests get their own preview environments, so changes are seen before they go live.
What it demonstrates
Building for a client, from brief to a site they run themselves Content management tailored to how an organisation works Low-cost serverless hosting on Azure CI/CD with staging, production and preview environments
Start with a conversation
Have something similar in mind?
Real-time data, unusual interfaces, integrations or automation: if it’s a problem software can solve, let’s talk about it.
No technical knowledge needed. No obligation.