Case studies / Thinking behind the work

How the work
comes together.

Projects are rarely just about making something look good. These case studies unpack the problems, decisions, systems and design thinking behind selected work from Bedah Graffix Works.

Design × Technology × Problem Solving Digital Products
Websites
Systems
UI/UX
Visual Communication
Featured case study / 01

RAO2026

Conference platform + visual communication system developed and maintained from February to October 2026.
Conference dashboard 2026
REGISTRATION
ABSTRACTS
PAYMENTS
APPROVALS
Role System Concept & Developer
Visual Communication
Technology Laravel
Bootstrap
Period Feb — Oct
2026
Scope Platform + Design
Maintenance
01 / Context

The problem wasn't just a website.

RAO2026 required a digital platform supporting the conference and memorial scheduled for October 7–10, 2026.

The project needed to bring several activities into one connected experience: registration, user accounts, dashboards, invoicing, payments, approvals and abstract submission and review.

Alongside the platform, the project required an ongoing stream of visual communication throughout the February–October development and maintenance period.

The system concept was developed in collaboration with Dr. William Dekker, a mentor and communication / PR specialist, before the development phase.
02 / The challenge

Turn multiple moving parts into one usable system.

01

Multiple user journeys

Participants, administrators, abstract reviewers and superadmins needed different capabilities.

02

Connected workflows

Registration, payment, approval, invoicing and abstract management needed to work together.

03

Communication at scale

The platform existed alongside a continuously changing calendar of visual communication.

03 / System architecture

One platform.
Different journeys.

The platform was developed using Laravel with Bootstrap on the frontend and the required supporting packages for the application's workflows.

01

Registration

User onboarding and account creation.

02

User Dashboard

Personal account and activity management.

03

Payments

Invoicing, payment and approval workflow.

04

Abstracts

Submission and administrative review.

05

Superadmin

Central visibility across platform activity.

04 / What was built

A platform around the people using it.

01

Landing page

Public-facing conference and memorial information and communication entry point.

02

Registration

User registration and authentication flow.

03

User dashboards

Logged-in users could access and manage their relevant activities.

04

Invoicing

Invoice generation and payment-related workflow.

05

Payment & approval

Payment and approval processes integrated into the platform workflow.

06

Abstract submission

Users could submit abstracts through their accounts.

07

Abstract review

Abstract administrators could review submitted material.

08

Superadmin

Central administrative visibility across users, abstracts, payments and other platform activity.

05 / Visual communication

The system needed a voice too.

From March through October 2026, visual communication was produced according to the project's communication calendar, alongside additional design requests.

Campaign / Timeline
Call for Papers
Conference Communication
Presentation / Event
Additional work included timeline updates, early-bird campaign assets, call-for-papers designs, concept PDFs, letterheads, banners, exhibition presentations, pitch presentations, memorial and conference concept design and other requested communication materials.
06 / From concept to maintenance

The project wasn't a handoff. It was a process.

01

Concept

System concept and requirements shaped with the project communication context in mind.

02

Development

Laravel application development, frontend implementation and workflow construction.

03

Testing

Platform flows, user journeys and administrative processes refined during implementation.

04

Maintenance

Ongoing updates and requested changes throughout the project period.

05

Communication

Continuous visual support around the project's communication calendar and evolving needs.

07 / Reflection

What the project reinforced.

Systems begin with people.

Before choosing technology, understand the people, roles and decisions the system needs to support.

Design doesn't stop at the interface.

Information architecture, workflows, permissions and communication are also part of the experience.

Real projects keep changing.

Maintenance isn't simply fixing things. It often means adapting a product as requirements evolve.

Technology and communication can reinforce each other.

A digital platform can provide the infrastructure while visual communication gives the project a consistent public-facing language.

09 / Start something

Your project could be the next
case study.

If there's a business problem, digital product, website or visual challenge you're trying to solve, let's talk about it.

Start a conversation ↗