I was thinking about this idea a lot the other day.
Currently I conceptualize the CMS like this: The creation of a collection creates a template (collection page). The Template then has to be used with that URL string. Unless the collection is for internal use then the generated template will remain blank and in the template list.
If we could create template pages independent of a collection then we could create designs that could fit multiple industries and flip the design on the fly for a new client. And it would allow us to create different sub-pages in the collection. This is very similar to the way Modx works and find it useful for larger sites.
When creating a page in the collection I imagine the only option would be to choose a template. Once the template is chosen the form fields that were set up for that template would appear.
Hope that's clear. It's clear in my head but hard to get out in writing.
Alex Nichol
0
0
This is a HUGE PAIN POINT. Please fix this or we need to cancel our subscription and look for other solutions.
Please make this happen
What's the point of a CMS if the records can only be viewed on a single page??
Is this going anywhere? I'm working with users with low tech literacy who sometimes want to print pages, and I'd like to make a "print-friendly" version of my collection template. The website also needs to exist in two languages, and I was hoping to have one collection (so my org partner can input the English and Spanish at the same time/in the same place) with an English and Spanish version of the collection template. This could also be used for light/dark modes. I really hope y'all are considering this!
yeah, this is ridiculous. How can you launch an eCommerce builder without multiple product page types? Clearly, it shows you only care about single merchant stores and we should look elsewhere for serious solutions.
I agree.
@webflow, if you want to compete with wordpress on cms, or watch cms clients defect, do this already.
I was honestly pretty shocked when I got to the point in using CMS features for the first time to see that not only is a 'collection page' created arbitrarily that you can only copy & paste content into, but that one page is the only one you get to have.
It seems like it must have been a consession of some sort, like maybe things didn't go well when they were creating that area of functionality... so they settled for a limited feature? Well, it's a basic feature, everyone here thinks so. There's 247 votes at the moment saying so. It's absence has shaken my confidence in Webflow altogether so much that instead of being enamored with it, as I was when I first discovered it, I'm now exploring alternatives.
This is a serious problem. Please fix it. We need collection template pages, like yeserday. F*ing Wordpress has you beat on this.
I have mini courses database with materials and videos. I display everything on my website, but only a few are available for non members.
I would like to display the same database with all the materials and videos on another page, which is shown only for members, in another URL. I'm using memberstack for that.
I was annoyed in the first place that it creates the CMS page "auto-magically" the moment you create a CMS. It was totally unexpected behavior, impossible to predict. That you can't have any control at all and have to expect irrational behavior combined shows that this is a very broken part of the UX.
I would love this, but for different languages. I would like to set up a collection with fields for each language, then having these templates showing just one language. So in my case, three templates per collection (Swedish, English, Serbo-Croatian)
I need this for Articles. I have multiple article types with essentially the same content, that require different treatments.
For example, standard articles vs features. The core content is the same, but features need a different, more dramatic layout. That said, I would like to load them all (both featured and standard articles) into one grid on a homepage for example.
I am shocked and disappointed this is not possible although I may be missing the correct workaround.
I spent so much time building the site to realize just now that we cannot do this :(
This also moves closer to solving the issue of not being able to feature more than one collection type in a collection grid. For example: if we build a landing page, a blog page and a normal page layout, but want to create a featured grid on the homepage. We can only feature one page type per collection.
best way to think about this is WordPress allows one to create template pages that make it easy for clients to create their own pages.
Best way to think about in terms of your goal here is Wordpress or better. Currently, your not to WordPress yet.
Best,
Nathan
That would actually solve my problem of having to separate lists and then not being able to sort the two separate lists as one list...each list needs to have it's own specific template with different 3rd party codes on the page yet it all belongs under 1 roof, so to speak so I don't want to lose the functionality of sorting...
Very cool idea. My customer wants a normal template and a landing page template from the same data. I have created another collection with references, but we are only allowed 5 fields...