Best Practices for Creating a Scalable Multi-Level CMS Structure with Relume in Webflow

AP · 2026-02-23T13:04:56.335Z

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.

Best Practices for Creating a Scalable Multi-Level CMS Structure with Relume in Webflow | Relume Community

3 comments

· Sorted by Oldest

Matt J.
·
·
AP I would think of the sitemap more about what page templates will I need, rather than an exhausted list of region or country inventory. If the structure of the page is not changing, but the content is, just call it a template in the sitemap and account for it, but you dont need to list every country or every region. What's not super clear with what you have currently is more from the user perspective. How is a user actually navigating this, and thinking about it from the user perspective, which in my opinion is more of what a sitemap should be about and not trying to be a documentation tool for how its going to look technically. Or an inventory tool for all the regions. How is the user navigating this website? If on the homepage, maybe we have a section that allows the user to choose a country and a region, and upon hitting submit, it loads in a list of golf courses and hotels. Or maybe the homepage is just listing out all countries and the user clicks on a country and is taken to a page with a list of regions and then the user has to click on a region and then they are taken to a page of golf courses and hotels filtered by that region. So then on that region template, I might have two lists or sections - one for golf courses and one for hotels. So then as a user, I click on a golf course, and it takes me to that golf course template filtered by region. /region/[region-name]/[golf course name] I'd have a countries collection, regions collection, golf course collection, and hotels collection. Each of these collections would have their own template page. The layout stays the same, the content changes. Golf course and hotel collections reference both the country and region collections. I think from a UX perspective the first option I presented would be best, but I dont have enough context to make that final decision. Here's an example of a sitemap that might make sense. If you are happy to provide more details or poke holes in my thinking, happy to continue this collaboration to see if there's a reasonable sitemap we can put together for your use case.
AP
·
·
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.
Matt J.
·
·
AP this to me feels pretty close to what you'd want to have based on what you've provided to me for a sitemap. I think conceptually, you are probably trying to create a conditional or loop - which we have no concept of in Relume. Everything is linear in our sitemap tool and I understand that there might be use cases where you'd have a fork that would then have a single destination, but in this case I think we can make this work by having the user choose which one they care about (golf course or hotel) at the region template page, and then the fork goes from there. What is not clear from this sitemap is the ability to click into a single hotel, or clicking on a link that takes you to "all hotels by region" - which I'm sure is exactly the issue you are having. There's no way to draw an arrow from one of the choices the user makes to either go directly to the details (individual) or to the all hotels. So we'll have to just create one path, and then speak to the other. Another option is to get as far as you can in Relume, and then bring it into Figma to create this IF statement.

Matt J.
·
·
AP I would think of the sitemap more about what page templates will I need, rather than an exhausted list of region or country inventory. If the structure of the page is not changing, but the content is, just call it a template in the sitemap and account for it, but you dont need to list every country or every region. What's not super clear with what you have currently is more from the user perspective. How is a user actually navigating this, and thinking about it from the user perspective, which in my opinion is more of what a sitemap should be about and not trying to be a documentation tool for how its going to look technically. Or an inventory tool for all the regions. How is the user navigating this website? If on the homepage, maybe we have a section that allows the user to choose a country and a region, and upon hitting submit, it loads in a list of golf courses and hotels. Or maybe the homepage is just listing out all countries and the user clicks on a country and is taken to a page with a list of regions and then the user has to click on a region and then they are taken to a page of golf courses and hotels filtered by that region. So then on that region template, I might have two lists or sections - one for golf courses and one for hotels. So then as a user, I click on a golf course, and it takes me to that golf course template filtered by region. /region/[region-name]/[golf course name] I'd have a countries collection, regions collection, golf course collection, and hotels collection. Each of these collections would have their own template page. The layout stays the same, the content changes. Golf course and hotel collections reference both the country and region collections. I think from a UX perspective the first option I presented would be best, but I dont have enough context to make that final decision. Here's an example of a sitemap that might make sense. If you are happy to provide more details or poke holes in my thinking, happy to continue this collaboration to see if there's a reasonable sitemap we can put together for your use case.
AP
·
·
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.
Matt J.
·
·
AP this to me feels pretty close to what you'd want to have based on what you've provided to me for a sitemap. I think conceptually, you are probably trying to create a conditional or loop - which we have no concept of in Relume. Everything is linear in our sitemap tool and I understand that there might be use cases where you'd have a fork that would then have a single destination, but in this case I think we can make this work by having the user choose which one they care about (golf course or hotel) at the region template page, and then the fork goes from there. What is not clear from this sitemap is the ability to click into a single hotel, or clicking on a link that takes you to "all hotels by region" - which I'm sure is exactly the issue you are having. There's no way to draw an arrow from one of the choices the user makes to either go directly to the details (individual) or to the all hotels. So we'll have to just create one path, and then speak to the other. Another option is to get as far as you can in Relume, and then bring it into Figma to create this IF statement.