ROOTS & RUINS
ROOTS & RUINS tells Angkor as an ongoing relationship between stone, forest, and community rather than a dead city invaded by nature.
01 · Direction
The journey moves from dawn to stone faces, circuits, and living culture, pairing religious meaning with on-site conduct.
The brief is to make a destination and hospitality platform that creates desire and helps visitors decide without assembling information from several places. ROOTS & RUINS is therefore treated as a content and conversion system, not a collection of attractive screens.
Guests choose a circuit by time and stamina, book licensed guidance, inspect light windows, and carry offline visit rules.
“For ROOTS & RUINS, aesthetics earn their place only when they make place, season, itinerary, conditions, and the on-site experience easier to see, understand, and act on.”
- Format
- destination and hospitality platform concept
- Audience
- Travellers choosing where, when, how, and what to book
- Primary proof
- Place, season, itinerary, conditions, and the on-site experience
- Primary action
- Build an itinerary, check availability, and reserve
02 · Dawn
Dawn should tell visitors what is worth remembering.
Dawn extends the hero promise into a situation a visitor can picture. For ROOTS & RUINS, the content needs to show what happens, why the detail differs, and which information matters enough to continue exploring.
In production, this module should offer a short scanning layer, deeper verification for people who need it, and a clear route forward. That structure preserves editorial pace without sacrificing search discovery or accessibility.
Principle: every artboard must add a reason to believe or a reason to act.
03 · Faces
Faces is not filler; it is evidence.
Faces is an evidence layer for ROOTS & RUINS's positioning. Instead of adding adjectives, the artboard uses place, season, itinerary, conditions, and the on-site experience to turn a visual impression into a reason visitors can remember and compare.
Every claim should carry a source, scope, and update date where relevant. That becomes essential when a concept moves towards production: trust comes from verifiable detail, not the volume of brand language.
Principle: every artboard must add a reason to believe or a reason to act.
04 · Circuit
Place circuit at the right moment in the decision.
At the centre of the journey, circuit classifies choices and reduces cognitive load. Primary information should scan in seconds; secondary detail opens after visitors know what they care about.
Headings, image captions, and contextual links also help search engines understand the page without keyword repetition. SEO is the outcome of clear information, not a text layer added after design.
Principle: every artboard must add a reason to believe or a reason to act.
05 · Living
Living connects brand story to action.
Living sits close to the moment a visitor considers “Build an itinerary, check availability, and reserve”. The artboard therefore keeps brand emotion while making conditions, the next step, and the post-click outcome explicit.
A live version should measure the primary action and hesitation signals: returning to an earlier section, opening support information, or leaving at a particular field. Those signals reveal missing content before button colour or CTA wording is optimised.
Principle: every artboard must add a reason to believe or a reason to act.
06 · closing invitation
Close with closing invitation, not an empty button.
closing invitation closes the story by recalling value already demonstrated rather than placing a button in empty space. Visitors should see a next action that fits the context and be able to return to decision information without losing position.
The final invitation should retain the spirit of “The jungle isn't destroying it. They're holding each other” while stating response time, required information, and alternatives. A good ending lowers uncertainty; it does not create artificial pressure.
Principle: every artboard must add a reason to believe or a reason to act.
Design language
Recognise ROOTS & RUINS before the logo has to appear.
The design language follows a folklore chronicle treatment, the concept palette, and its native image rhythm. The goal is not novelty in every section but a small set of rules strong enough to support new content.
- 01
Contrast with a job
Accent colour is reserved for attention and primary action; background, type, and imagery stay stable so ROOTS & RUINS never becomes noise.
- 02
An industry-specific rhythm
Image ratio, paragraph length, and headline placement follow how people actually explore a destination and hospitality platform, not a universal portfolio template.
- 03
Evidence before invitation
Place, season, itinerary, conditions, and the on-site experience arrives before the CTA, making action a reasonable consequence of the story rather than an interruption.
Colour system
#101008
#302820
#484038
#605850
#787068
Colours come directly from ROOTS & RUINS's art direction. Production should validate WCAG contrast for copy, interaction states, and charts instead of assigning every colour equal weight.
Production direction
Turn the concept into a system with content, data, and clear ownership.
The visual design is an opening hypothesis. A live version must be tested with real content, real behaviour, and the technical constraints of the team that will maintain it.
- 01
Inventory content and data
Identify the source, update cadence, and approver for place, season, itinerary, conditions, and the on-site experience before finalising page architecture.
- 02
Prototype the primary flow
Test “Build an itinerary, check availability, and reserve” on real devices, including missing data, failure, and interrupted-return states.
- 03
Performance and access
Serve images at display size, preserve semantic HTML, support keyboard use, and respect reduced motion so the experience does not require powerful hardware.
- 04
Measure what matters
Track exploration depth, saved itineraries, and completed reservations, exclude internal traffic, and agree event definitions before interpreting results.
Frequently asked questions
Questions to resolve before producing ROOTS & RUINS.
- Who is ROOTS & RUINS designed for?
- Travellers choosing where, when, how, and what to book. Every layout decision serves one primary action: build an itinerary, check availability, and reserve.
- Why does this detail page differ from the other concepts?
- The folklore chronicle treatment follows how people explore a destination and hospitality platform, its information density, and its particular visual language.
- Could the concept become a real website?
- Yes, after replacing assumptions with real content, data, legal requirements, and the organisation's “Build an itinerary, check availability, and reserve” process.
- How should effectiveness be measured?
- A useful starting set is exploration depth, saved itineraries, and completed reservations; final targets must follow the real operating model.
Continue exploring
More concepts in the field, each with a different answer.
From concept to product
Have an idea that needs to become a real website?
ToanKhonTech can shape positioning, content architecture, conversion flow, and an interface system for your actual context—without copying a fictional concept wholesale.