← All work 02 · Public service digitalisation

Desa Tulusbesar

Village profile and administrative service site, from research to handover.

5 pages · 4 hamlets · manual book

Role Project Lead · Frontend · UI/UX · Backend Team 8 people Period July — August 2026
View live ↗
Laravel Filament Tailwind WebGIS Docker
Desa Tulusbesar — Public service digitalisation
Village history, editable by village staff
Village history, editable by village staff
Tourism and culture storefront
Tourism and culture storefront
Small-business directory, including the tofu centre
Small-business directory, including the tofu centre
WebGIS map of the four hamlets
WebGIS map of the four hamlets
6.543 Residents served
4 Hamlets mapped
8 Team members
1 Formal handover
Role
Project Lead
Team
8 people
Duration
2 months
Status
Live & handed over

Context & problem

Desa Tulusbesar has 6,543 residents across four hamlets. Information was scattered across notice boards and chat groups, and residents visited the office just to ask about requirements. Tourism and small businesses had no digital storefront.

Role & responsibilities

I led a team of eight and owned scope, work allocation, and the relationship with village staff. I also built the frontend, the UI/UX design, and part of the backend.

Planning

We started from staff interviews, then sorted findings into three layers: must exist before handover, important but can follow, and future ideas. The timeline ran backwards from handover with one week of reserve.

Coordination

The team was split by track — village content, public interface, admin panel, WebGIS map — with one owner each. I was the single contact for village staff so they never received conflicting requests.

Progress monitoring

Monitoring happened through live walkthroughs with village staff. Unclear buttons, foreign terminology, and overlong flows became a prioritised fix list immediately.

Handover

Done meant village staff could manage content themselves. We prepared a manual book, a short training session, and a handover document; the site is live at tulusbesar.com.

Risks & responses

Risk Village requirements changing after seeing early results.
Response Scope split into three layers with a one-week buffer before handover.
Risk Village content and photos unavailable when development started.
Response Content track separated from the technical track so development was not blocked by assets.
Risk Village staff struggling to manage content independently.
Response A simplified admin panel plus a manual book and a hands-on training session.

Outcomes

  • Website live at tulusbesar.com and used as the village’s official information channel.
  • Administrative requirements can be viewed and downloaded without visiting the office.
  • Tourism, culture, and small-business potential have a digital storefront, including a WebGIS map.
  • Formally handed over with a manual book so the village can manage content independently.

What I would do differently

A post-release audit found two defects that slipped through: the document download button showed “File not yet on server”, and document categories still contained test data. The lesson is clear — I tested the flow as a developer, not as a resident opening the site on a phone with a slow connection. Going forward I will build the release checklist from the end user’s point of view and have someone other than the feature’s author run it.

Artifacts

Documentation reconstructed from project archives for portfolio purposes.