Algeria–Switzerland Community, Switzerland
Swiss Algerian Community Platform
A membership and events platform for the Algerian community in Switzerland: approved membership, event registration, donations, QR-bill payment and targeted email and SMS notices.
- Status
- Completed
- Industry
- Non-profit & Community
- Year
- 2024
- Categories
- Web Applications, Social Platforms
A platform an association can actually run itself
A French-language membership, events and donations platform for a diaspora association, built from a Figma design with approved membership, QR-bill payment and targeted notifications.
Community matters most to people who share a background and live somewhere else. The Algerian community in Switzerland had the bond already; what it did not have was somewhere that held it — a place that says publicly who they are, and does the unglamorous work of running an association underneath.
What it does
The public side presents the association: its identity, its statutes, its members, its cultural writing, and the events it runs. The member side handles the mechanics — registering, being approved, signing up for an upcoming or recurring event, cancelling a registration when plans change, and donating.
Administrators can send email and SMS to targeted groups of members rather than everyone, which is what makes a notice about a specific event worth sending at all.
Event attendance is paid and ticketed: the platform issues a Swiss QR-bill for payment and a ticket carrying its own QR code for the door.
The site is French-language throughout, which is the language the community actually organises in.
We worked from a well-made Figma design and built it in Laravel.
- Membership
- Application and approval
- Payment
- Swiss QR-bill and QR ticket
- Notifications
- Targeted email and SMS
The problem
An association's real work is administrative: knowing who the members are, telling the right ones about the right event, taking money for a ticket, and knowing who is coming.
Done with a mailing list and a spreadsheet, each of those is a manual task that lands on one volunteer, and the failure mode is quiet — a notice that went to everybody and was ignored, a registration nobody recorded, a payment nobody reconciled.
There was a second requirement that carried as much weight as any of that. The site had to represent the community well publicly — a diaspora association's website is part of how it exists at all.
Requirements
- Present the association's identity, statutes and membership publicly
- Let visitors register as members and administrators approve them
- Publish one-off and recurring events with dates, venues and descriptions
- Let approved members register for events and cancel a registration
- Take donations from members
- Take event payment via Swiss QR-bill and issue a ticket with a QR code
- Let administrators send email and SMS to targeted groups, not the whole list
- Build to the supplied Figma design, in French
The solution
Membership is an approval flow rather than a signup. Anyone can apply; an administrator decides. That single decision is what makes every downstream feature safe — targeted mail goes to a known list, and event registration means something.
Events model both one-off and recurring occurrences, because an association's calendar is mostly the same commemorations each year alongside the things that happen once. Registration is reversible by the member: cancelling is a first-class action, not an email to a volunteer.
Payment follows the Swiss standard rather than a bolted-on card flow. The platform generates a QR-bill with the association's account details and the payment reference, which is how people in Switzerland expect to pay and how the treasurer expects to reconcile. The ticket issued against it carries a QR code for the door.
Notifications are targeted by design. The administrator chooses the recipients, and the same message goes out over email and SMS — SMS because a notice about tomorrow evening is not an email.
Architecture
A Laravel application on MySQL, running on Linux, with the front end built directly to the Figma design.
Email and SMS both run through queued jobs rather than the request that triggered them, so an administrator sending to a large group is not waiting on a delivery provider, and a failed send is retried rather than lost.
The public site, the member area and the administration area are separated by role, with the membership approval state as the gate between visitor and member.
Implementation
The design was already good, which changes how you build. The work was to realise it faithfully rather than to negotiate with it, and to keep it intact once real content — long French event titles, photographs of varying quality, articles of different lengths — arrived in the layout.
Content is the site's actual product. Alongside events, the association publishes cultural writing on Algerian history, food and music, and the home page gives that as much room as the association's business. That balance was deliberate: a site that only ever asks members for something gets visited only when it asks.
French throughout, with the language toggle in the header, because the community organises in French and an English-first build would have been the wrong artefact.
Results
The platform is live at sac-dz.ch and is the association's public presence and its administrative system: membership, its published events, ticketing and donations all run through it.
It carries the association's real calendar — general assemblies, commemorations, the Ramadan ftour, a meeting with a visiting Algerian minister — which is the only proof that matters that the event tooling fits how they actually work.
What we learned
Building to a strong design is faster than designing while building, and the discipline it imposes is worth more than the freedom it costs.
Following the local payment convention mattered more than offering more payment options. The QR-bill is what Swiss members and Swiss treasurers already know how to handle.
Approval before membership looks like friction and is actually the feature. Every targeted notification and every event registration downstream depends on the list being real.
Gallery