Skip to content

PRESEC

Three of our products, inside a school’s own site

PRESEC Legon’s Students’ Representative Council runs its site, its award voting, its events and its fundraising from one place. We built the site; the voting, tickets and giving underneath it are BloomBallot, BloomEvents and BloomFund.

The PRESEC SRC home page

The brief

A council that changes every year, for a school that has been here since 1938.

The Students’ Representative Council hands over to a new executive every year. The school it represents was founded in 1938 with sixteen boys and four teachers, and has a long record to show for it.

The site had to hold both: the school’s history, its executives past and present, its achievements and its alumni — and be run by the council and staff without a developer.

The history timeline on the PRESEC SRC site

What we built

An admin the council runs itself.

News with drafts and categories, yearbooks as page-turning flipbooks, and the whole About section — history, current and past executives, achievements and alumni — are all edited from one admin.

Changes reach the live site as soon as they are saved.

The current SRC executives, managed from the admin

Our products inside it

The school’s own pages, our products underneath.

Award voting runs on BloomBallot. The site draws its own nominee pages from BloomBallot, and BloomBallot counts the votes and takes the payment. Voters without data dial *920*164# instead.

Events and tickets come from BloomEvents the same way: the school’s own ticket form, our checkout behind it. Donations run on BloomFund — the council starts a campaign by pasting its embed into the admin.

BloomBallot and BloomEvents are called server to server with their own keys, and BloomFund runs in its own frame, so the school’s site never handles a payment itself.

A BloomFund campaign on the PRESEC SRC donations page

What changed along the way

We deleted the events editor we had built.

The first version had its own events editor. Once BloomEvents could be embedded, we removed it and moved events across, so tickets, door scanning and payouts are handled by a product we already run rather than a second copy of one.

Organisers also decide whether the public sees vote counts, percentages or nothing. Hidden counts are removed on the server before the page is sent, so they cannot be read out of the browser.

Where it is now

One site to everyone who uses it.

Votes, tickets and donations run on BloomBallot, BloomEvents and BloomFund, behind PRESEC’s own pages and under its own name. To the people voting, buying a ticket or giving, it is all one site.

Got something shaped like this?