Designing Nested CMS Collections

Design help CMS
1

Hey guys,
I am new to webflow and need your help.
I’m working on the project of migrating the current website (www.owox.com) now and I need your help designing the CMS collections for the blog posts.

So the current website architecture we have makes the URLs like this:
/blog/articles/article-name
/blog/use-cases/use-case-name
/blog/success-story/client-name

Plus we also have the URLs like
blog/topic/topic-name but that’s another story.

So the idea is that all of the blog posts (articles, use-cases, success-stories) - they have the same database structure.
So they are all blogs…

But how do I structure all that withing webflow?

I was thinking of creating a cms collection/database called “Blog Posts” and then filtering it all out on the pages by some condition,
but with this, I won’t be able to keep the URL structure of
eg /blog/articles/article-name
as articles/article-name would have to be the Slug,
which is not handleable within webflow…

Any ideas?

3

Webflow’s collection sligs are hard-bound to the collection, which means that there are only two approaches in Webflow currently;

You can create a collection for each path you want, with the first part of the path as static;

/blog/articles/(article-name)
/blog/use-cases/(use-case-name)
/blog/success-story/(client-name)

This would require 3 collections, one with the slug articles, one for use-cases and one for success-story, even though they effectively use the same blog schema. All 3 would be under the folder named blog.

The second option is to build a layer on top of Webflow’s hosting known as a reverse proxy, which rewrites and redirects all paths so that you can create the structure you want.

I do these builds for clients occasionally, they’re a bit of work depending on the path structure you want. You can learn a bit more here if this is a critical feature for your site.

1 Like