elektra.io, a website that does everything
The website for Elektra, the student association for electronics students at NTNU. Built from scratch: frontend, backend, database, auth, billing, event management, the whole thing. It started as a redesign and turned into the operating system of a student association.
Live preview at elektra.io.
What it does
- Accounts & roles: Full user hierarchy. Groups, roles, admin levels, public vs. private profile fields.
- Events: Create, edit, price, locate (on a custom campus map or via Google Maps off-campus), gate by group, cap attendance, ticket via QR codes branded with the Elektra logo.
- Billing: Receipts post directly into the økonomiansvarlig's accounting software.
- Job posts: stillingsannonser, oppslag, classifieds, with moderation.
- Calendar: All events in one view, filtered by group.
- POV: An event-photography mode where attendees can shoot but not see photos until the event ends.
- Help & access: User manuals; room-access requests routed to the right approvers.
- Theme: Full dark mode. Seasonal animated backgrounds: snow in winter, hearts on Valentine's, ghosts at Halloween.
- Profile: Custom profile pictures, descriptions, public and private contact info, allergies for event hosts.
- Auth: Google sign-in plus an internal flow.
- Safety: Sensitive fields encrypted at rest; least-privilege role checks at every endpoint.
- Ops: Separate dev environment at dev.elektra.io; deploys via CI.
What it taught me
Building software for a real community is a different game from building it for yourself. Every feature touches a real person's evening or wallet. The biggest change in how I write code came from this project: less cleverness, more clarity, far more tests around the bits where money and access live.