TiyoouwBahasa IndonesiaStart a brief

← All work

Case study · Design + Build · 2026

himasif.id

The student association's website and CMS: news, programs, a store, elections, email campaigns and small tools like short links and a paste bin.

Client
HIMASIF, Universitas Jember
Role
Front end and back end
Platform
Website + CMS
Year
2026

Visit himasif.id (opens in a new tab)

himasif.id: Association website, CMS, e-voting and email campaigns.

In short

Problem
Elections and announcements for hundreds of members, in one trusted place.
What I did
Front end and back end: e-voting, the results reveal, CMS and email campaigns.
Result
Live at himasif.id, with about 500 members of the four active cohorts using the e-voting.

01The problem

A student association runs elections, programs and announcements for about 500 members across four active cohorts. It needed one site for all of it, and an election its members could trust.

02My role

I update and extend both halves: the Nuxt front end and the Laravel back end with its CMS, including e-voting and email campaigns. The front end is a team codebase, and I work alongside other members.

03What I built

  • E-voting

    Magic-link sign-in, a proof-of-vote code for every voter, scheduled, open, closed and announced phases, and graceful retries when traffic spikes.

  • The reveal

    A results reveal for the chair election, timed to music, for the moment everyone is watching.

  • Email campaigns

    Campaigns sent from the CMS to the four active cohorts: e-voting for the new chair, event posters and invitations.

  • Short links and paste

    Short links resolve on the server, and the paste bin stays on himasif.id instead of bouncing to the API domain.

  • Secrets off the client

    The API key moved out of the public JavaScript into a server proxy.

  1. ScheduledVoters get a magic link
  2. OpenOne vote, one proof code
  3. ClosedResults stay sealed
  4. AnnouncedThe reveal plays
The four phases of an election on himasif.id.

04Design decisions

  1. Trust before speed

    Each voter gets a proof code, and results stay sealed until the announced phase.

  2. Make the result a moment

    The reveal is staged like a show, with a white slide-up timed to the music.

  3. Secrets stay on the server

    The browser never sees the key; a small proxy adds it on the way to the back end.

05Stack

Front end
Nuxt 3, Vue 3, Pinia, Tailwind, Vercel
Back end
Laravel API and CMS (separate repo)
Tests
Unit tests for the voting flow

Start a brief

Pick what's easiest. I usually reply the same day.