I love this example by Matt. It's from before we could nest collection template pages inside folders so you'll notice a "flatter" URL structure such that the URL pattern doesn't match the breadcrumb pattern. Unfortunately I couldn't get it to work with the nested example since a category CMS like "media-types" will have it's own URL even if we nest it within content. You could set up the link in the CMS but then you lose the benefit of matching routes in staging + production. I've seen the flat URL structure work just fine for SEO in client projects, so I can happily recommend Matt's solution if your CMS structure supports (it's the best setup for ecom for sure). I have some clients with strict URL structure requirements though in which case I'm using this setup. Maybe I'm missing something? A nifty trick? If you discover anything else let me know and thanks for sharing!
Thank you for this video. I’ve got a question: does this method work on static pages? Because I’ve found lots of breadcrumbs tutorials for CMS collections and Ecommerce, and none of them mentions the case when all of the pages are static 🥲
I love being validated. I built my breadcrumb component EXACTLY like this before I ever saw this video. Thank you!
Good morning 👑 🤝
so soo goood! Thank you for this ✨
Would love to see your approach on adding and styling an audio player in webflow
This content is GOLD! 🙌
glad it helped! Good way to flex those component muscles too :).
Thank you So much for this tutorial
Glad it was helpful!
Everything you post is so helpful. Yeeeeeee 🔥 🤙🏽
Glad to hear it!! Feel free to suggest other topics 💯
ho do you have "content," page and then also, "content," folder? would the content folder be the page?
nope! content folder just creates the route not the page.
thanks!!!
Thank you 🙏🏻
What do you think about this method: ruclips.net/video/mFF5jaGGqfA/видео.html - via reference links inside cms collection
I love this example by Matt. It's from before we could nest collection template pages inside folders so you'll notice a "flatter" URL structure such that the URL pattern doesn't match the breadcrumb pattern. Unfortunately I couldn't get it to work with the nested example since a category CMS like "media-types" will have it's own URL even if we nest it within content. You could set up the link in the CMS but then you lose the benefit of matching routes in staging + production.
I've seen the flat URL structure work just fine for SEO in client projects, so I can happily recommend Matt's solution if your CMS structure supports (it's the best setup for ecom for sure). I have some clients with strict URL structure requirements though in which case I'm using this setup.
Maybe I'm missing something? A nifty trick? If you discover anything else let me know and thanks for sharing!
Thank you for explanation 🙌🏻🙌🏻🙌🏻 Great tuts you do) You are Legend!))) Learn a ton from you!
Breadcrumbs = 👍, Cookies = 👎
never would think I would hear you say this. Confusers are confusing.
Contusors are contusin 😔
Thank you for this video. I’ve got a question: does this method work on static pages? Because I’ve found lots of breadcrumbs tutorials for CMS collections and Ecommerce, and none of them mentions the case when all of the pages are static 🥲
I'm using CMS in this example. You could do it for static pages but it would require some manual labor, or Javascript :).
Thanks for answer @@webbae
Hey I created the same way but my blog home page is getting redirected s /blog/blog
maybe remove the /blog from one of the links? The paths are relative so that might do it!