Perkantas Yogyakarta

A little context

Perkantas Yogyakarta is a community web platform supporting Christian discipleship activities for students, alumni, and medical professionals.

My part: Frontend development for the initial 2023 build. In phase 2 (March–June 2026), I handled maintenance, API migration work, database work, deployment, and system stabilization.

What needed attention

The platform was already in use. I needed to fix existing issues and update the frontend without disrupting everyday community tasks.

Delivery Journey

1. Initial frontend build
2. Ongoing maintenance
3. UX audit and stabilization
4. Modernize interfaces

Key Decisions

01

Usability

Readable community pages

Use readable, responsive layouts for everyday community tasks.

02

Delivery sequencing

Stabilize before modernizing

Resolve issues in the existing platform before expanding migration work.

03

Maintainability

Reusable layouts

Keep repeated pages consistent as components move from Bootstrap to Tailwind CSS.

Implementation Evolution

01

Initial build · 2023

Translated approved designs into Laravel Blade and Bootstrap interfaces and handled domain, hosting, and ongoing maintenance.

02

Phase 2 · March–June 2026

Audited user flows, refactored interfaces with Tailwind CSS, and prepared components for API-based integration. Also handled database work, deployment, and system stabilization.

Coming Back to Something I Built

The first version went live in 2023, with approved designs built in Laravel Blade and Bootstrap. Returning to it in 2026 meant working with something people were already using. Any changes had to make room for that.

I started with fixes and stabilization before the broader migration work. Then I refactored repeated interfaces with Tailwind CSS and prepared components for API integration.

It meant keeping the existing pages working while introducing newer patterns. There was plenty of less-visible work along the way: compatibility checks, regression testing, and deployment.

The UX audit, maintenance work, and collaboration with QA shaped this phase. I don’t have comparative usability results to share, so this is the story of how the platform evolved, with that question still open.

Testing Strategy

Worked with QA on regression checks and API validation, and performed unit testing for CMS CRUD functionality. These checks supported changes to an existing live system.

Before vs After

01

Starting point

Before

An existing Bootstrap-based platform needed stabilization and more consistent user flows.

02

Delivered work

After

Refactored interfaces, updated dependencies, and API-ready components supported continued maintenance.

What’s there, and what I still want to learn

The 2026 work brought refactored interfaces, updated dependencies, and API-ready components, alongside database work and deployment support.

I worked with QA on regression checks and API validation, and tested CMS CRUD functionality. Those checks mattered for keeping an existing system working; they don’t tell me whether the everyday tasks feel easier now.

I’d like to compare those tasks with people using the platform. I don’t have task-completion, support-volume, or satisfaction results to share yet.

What stayed with me

This was my first freelance project, and I continued maintaining it after launch. Returning in 2026 meant revisiting earlier decisions, discussing changes with the client, and fixing existing issues before moving on to the migration.

The people I worked with