Curug Hunter Jabar

Why it exists

This project came from a question I genuinely cared about: why is it still hard to find reliable waterfall information around West Java?

Discovery content often looks complete until you try to plan a visit. Then small details become important. Where is the place? What should you expect? Is the information clear enough to make a decision?

What I worked on

I treated Curug Hunter Jabar as my own product. I shaped the experience, built across the stack, organized the information, deployed it, and kept making decisions after the first version existed.

That ownership made the work different. There was no clean handoff where my responsibility ended. The interface, content quality, technical choices, and deployment all affected the same visitor experience.

Decisions that mattered

The platform needed to make destinations feel inviting without hiding practical information. I organized each destination so the visual sense of discovery and the details needed for planning could support each other.

I also kept the experience lightweight. A local discovery site should be useful on a phone and on an imperfect connection, not only on a fast laptop.

Where it stands

Curug Hunter Jabar became a real product-like website rather than staying an unfinished idea. It represents a step forward in my ability to own a project from curiosity through deployment.

What I learned

Shipping changed my questions. I stopped asking only whether I could build a feature and started asking whether the information was useful, whether the site was maintainable, and what I would improve after someone actually used it.