Skip to content
The top of the Rio Putovanja home page: a full-screen photograph of a traveller above a river canyon under the headline “Gdje počinje tvoja priča?” and a button through to the trips.

Rio Putovanja

Trip catalogue and admin panel for a travel agency in Bosnia

Before
A trip lived in four places: the programme in Word, the price in Excel, the post on Facebook, the bookings in email.
After
One record holds the trip. Change the date once and the page, catalogue card and booking total update automatically.
A departure page for Colombia: a street of painted colonial balconies below a mountain, the headline “Ritam latinske Amerike” over it with the country, the guide and the dates as pills beneath, and a bar fixed to the foot of the screen carrying the trip length, the price and an enquiry button.
The day-by-day programme: fifteen day tabs with day two open, its summary and the day's activities on the left, the full description of the day in a card on the right, and a progress bar reading “Dan 2 od 15”.
The destination map: a textured globe on black under the heading “Gdje vas vodimo?”, carrying a pin for every destination — green for the departures now running, gold for the places the agency has already been.

The team can update all content without developer support.

The admin panel's dashboard, drawn: a rail of destinations, future trips, reservations, statistics, journal and team, four tiles counting eighteen destinations, eleven running now, four sold out and six future trips, then the newest bookings with their party sizes and statuses beside the trips last edited with theirs, and a row of quick links.
The departure editor, drawn: eight tabs for the basics, media, itinerary, details, featured, general information, reviews and settings, with the trip's name, dates and price filled in and its days listed below as rows that drag into order. On the right the draft switch is on, so nothing of this trip exists for a visitor, and beneath it the trip's web address with the previous address kept as a permanent redirect.
The reservations queue, drawn: a search across name, email and telephone, filter pills counting a hundred and forty-two bookings by status, and rows beneath. The top one is open into three columns — who is travelling and how to reach them, which trip and the question they asked, and the four buttons that move the booking to contacted, confirmed or cancelled.
The statistics screen, drawn: tiles for a hundred and forty-two reservations, three hundred and eighteen travellers, eighty-seven future-trip enquiries and a forty-one per cent conversion, then a list of every destination with its bookings and travellers broken down into new, contacted, confirmed and cancelled, and an export beside it.

What was built.

Departures
A whole trip from one form: programme, guide, price, dates, capacity and status.
Drafts
A trip stays invisible until it is published: no card, no sitemap entry, no page.
Addresses
Rename a trip and the old link redirects for good, so shared links keep working.
Bookings
Every booking lands in one queue with the trip, the party size and a status.
Statistics
Reservations, travellers and conversion per trip, exportable as CSV.
Blog
The agency writes and publishes its own travel guides, filterable by continent and destination.
Scope
Domain, hosting, design, build, admin and deploy.
Afterwards
Still maintained: updates, patches and content edits when they need them.

From no site to selling out trips, run by the agency itself.