The ability to have multiple page templates per collection.

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
  • Jan 18 2017
  • Joe Shashati commented
    31 May, 2023 04:19pm

    Use cases for this are pretty limitless. Feels backwards that this feature is not available. This would also allow us to create secondary pages from within the collection template. For example a collection item would generate two pages, one that is the main landing page and second with a call to action that you can access from the first. Currently it looks like I have to manually create those pages every time a collection item is recorded. I see about 400 people wanting this feature, why is it still not available?

  • Axel Vaindal commented
    23 Mar, 2023 07:07pm

    This is clearly mandatory in order to create programmatic SEO pages, and target multiple keywords combination based on CMS items data.

  • Chris Guest commented
    15 Mar, 2023 04:34pm

    This would be helpful to allow an editor to input content once that feeds two different pages and use cases with the same slug for predictability.

    Consider a restaurant database that has a /location/[slug] page for potential diners to find a restaurant, then a different page /thankyou-offer/[slug] to show an offer or discount code to people that DID dine there.

    An editor listing a new restaurant could make one CMS entry, listing both the name and address of the restaurant for the location finder view, and the discount code and thank you offer at the same time.

    Then two different template pages could pull their relevant fields from the same CMS collection item, but have the SAME SLUG but with a DIFFERENT PATH.

    For example.

    The reason this is valuable, is that at the moment the editor creates the restaurant listing, both pages are created without double entry or risk of forgetting to create one or the other.

    Also, the URL structure and slug is predictable, so if any external software points to this content, it can deduce the /thank-you/ slug address from the /locations/ slug for each item, and vice-versa.

    There is specific benefit in one CMS collection driving two different templates with different URL addresses, rather than say one URL with a query string at the end, or a conditional display set within one template. This would make it easier and cleaner to report on traffic to the two different use cases, and also pixel/tag the templates differently, for example to retarget pre-diners differently to post-diners in paid media.

    Is this already possible via any other means? If so, please let me know.

  • Michael Moran commented
    8 Mar, 2023 08:44pm

    Please this would be so helpful as I am trying to make regional templates and links for versions for every item in a collection

  • Michael Egner commented
    16 Nov, 2022 10:44am

    This is much needed in my opinion. Been a while since this started!

  • Aurimas Slapšys commented
    19 Oct, 2022 08:25am

    We need this functionality to create a custom summary of the page and print it as PDF and different designs for some portions of the collections

  • Christopher Dell commented
    11 Oct, 2022 08:54am

    We need to have SEO pages for each of clients PER collection. Unusable to not have this.

  • Peter Robineau commented
    15 Sep, 2022 03:03pm

    This is a HUGE PAIN POINT. Please fix this or we need to cancel our subscription and look for other solutions.

  • Remo Moser commented
    11 Aug, 2022 11:37am

    Please make this happen

  • John Thorne commented
    24 Jul, 2022 06:32pm

    What's the point of a CMS if the records can only be viewed on a single page??

  • Kelsie Thomas commented
    11 May, 2022 03:11pm

    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!

  • Cookies & MILK commented
    23 Mar, 2022 06:46pm

    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.

  • Robert Turner commented
    11 Nov, 2021 04:44am

    I agree.
    @webflow, if you want to compete with wordpress on cms, or watch cms clients defect, do this already.

  • Roy Wilkie commented
    17 Dec, 2020 10:36pm

    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.

  • Renato Carvalho commented
    27 Oct, 2020 12:55pm

    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.

  • His Royal Meatbag Seph Reed commented
    29 Jun, 2020 12:25am

    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.

  • Erik selmanovic commented
    5 Feb, 2020 09:39am

    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)

  • William Valvo commented
    2 Dec, 2019 09:48pm

    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.

  • John T. commented
    10 Apr, 2019 05:19pm

    I spent so much time building the site to realize just now that we cannot do this :( 

  • Nick Fry commented
    15 Aug, 2018 07:23pm

    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. 

  • Load older comments
  • +340