Hi Matt J. — thank you. I appreciate you taking the time to provide such a detailed response this is helpful. I completely agree with your point about thinking in terms of page templates rather than inventory. I’m not trying to list every country or region in the sitemap — I understand those would be handled via Collections and their respective template pages in Webflow. So in principle, I’m aligned with: Countries collection → Country template Regions collection → Region template Golf Courses collection → Course template Hotels collection → Hotel template And that the layout remains fixed while content scales. My main question is more about how best to represent the user journey in Relume’s sitemap tool so that it clearly reflects the hierarchy without flattening it. The intended UX flow is: Home → Country → Region → Region page showing preview sections for Golf Courses and Hotels → Dedicated “All Golf Courses in [Region]” page → Dedicated “All Hotels in [Region]” page → Individual Course / Hotel pages I want to ensure the sitemap cleanly represents: Country template Region template Region-level Golf Course listing template Region-level Hotel listing template Individual detail templates From your experience, what’s the cleanest way to model that inside Relume’s sitemap view so the hierarchy is clear but not overcomplicated? Also, from a UX standpoint, would you recommend: A) Home → Country → Region → Listings or B) A home-level filter/search that immediately surfaces region-level courses and hotels? My priority is clarity and scalability over reducing clicks. Appreciate your guidance.
Hi Team We’re currently building a Webflow project using Relume and are running into difficulty generating a clean multi-level destination structure. Our site requires a 3-tier hierarchy: Country → Region → → Regional Golf Courses page → Regional Hotels page → Individual Golf Course / Hotel pages Each Region must have dedicated Golf Courses and Hotels sub-pages filtered to that region only (no global “All Courses” or “All Hotels” pages). The structure also needs to scale to 100+ regions. We’ve tried prompting this directly, but Relume seems to flatten or simplify the structure. Given Relume’s current capabilities, what’s the best way to approach this? Any guidance on best practice for multi-level CMS structures would be hugely appreciated. Thanks in advance 🙏 I have attached my prompt and the sitemap it generated to this message.
