Best way to structure travel content for intent-driven experiences?

I’ve been exploring how to better structure travel-related content so it aligns more closely with real user intent rather than just static destination pages.

For example, users today are searching for very specific queries—like airline policies, visa requirements, multi-city routes, or realistic itineraries—rather than just “things to do” in a city.

Some approaches I’ve been testing:

• Building query-first content instead of generic guides
• Structuring destination data (attractions, logistics, timelines) in a reusable format
• Keeping content modular so updates (like travel rules) don’t break the system

Recently, while working on a travel platform called Trekhops, I’ve been trying to implement this kind of structure more actively—focusing on how users actually search rather than how content is traditionally organized. It’s been interesting to see where this works well and where it gets challenging.

For those using Adobe Experience Cloud or similar ecosystems:

• How are you handling dynamic, intent-driven content?
• Are you using any structured data models or personalization strategies?
• What challenges have you faced when scaling this type of content?

Would really appreciate any insights or examples.