Sogod Travels

What the application is

Brought scattered attraction, route, and accommodation information into one manageable tourism-site concept for visitors to Sogod, Southern Leyte.

Who it was built for

Capstone tourism project concerning Sogod, Southern Leyte

My role

Web developer responsible for feasibility research, gathering destination information, implementation, and interactive route features

The problem

Travelers lacked one dependable place for verified attraction, route, and accommodation information about Sogod.

What I learned from the existing workflow

• Travelers need the information, while a local administrator would maintain it.
• Details come from attraction research, routes, nearby accommodations, and local sources.
• Scattered or outdated posts can make trip planning slower and less reliable.
• The capstone needed to be completed on schedule and remain manageable by non-developers afterward.

The solution

I paired each attraction’s descriptive information with practical route and accommodation guidance, then placed the content in a publishing setup that a non-developer could maintain. This connected discovery, trip planning, and future content ownership in one experience.

Key decisions

1. Use one managed source Central editing reduces dependence on disconnected posts and makes updates easier.
2. Put maps beside destination details Visitors can move from discovery to practical route planning in the same experience.
3. Choose an easy-to-manage publishing setup Future content updates should not require a developer for every change.

Result

Produced a manageable tourism site concept that combines locally maintained attraction information, route guidance, and nearby accommodation details. Public adoption was not measured.

What I learned

A tourism site depends as much on trustworthy content ownership as on presentation. Clarifying who maintains information is part of designing the product.

A closer look