Shared CMS across multiple sites

Some of the benefits:

  • This will be extremely useful in various scenarios like --multi-website, multi-brand with shared content
  • Will also avoid repetitive work in certain situations
  • Will enable a lot of interesting possibilities
  • Tarang Sanghi
  • Feb 15 2017
CMS
  • Post comment
  • Matthew Semik commented
    29 Feb 02:31

    Please

    Attachments Open full size
  • Dan David commented
    December 20, 2023 15:55

    !

    Attachments Open full size
  • Dan David commented
    December 18, 2023 21:14

    👍

    Attachments Open full size
  • Rollchair commented
    October 25, 2023 10:14

    Yes it would be cool to have one Master-Layout and Set-up and share or update on the other pages

    Attachments Open full size
  • Mario P. commented
    May 21, 2023 22:18

    Yes!

    Attachments Open full size
  • Aditya Pande commented
    January 24, 2023 14:22

    My company just told me to create 100-200 websites. This can't get any quicker.

    Attachments Open full size
  • William Gomes commented
    September 16, 2022 14:39

    This will be so useful!

    Attachments Open full size
  • David A Richardson commented
    August 23, 2022 01:41

    I'd like to see this too. I set up a subdomain for data uploaders that is not suitable for public viewing - more a "back end". Two sets of cohorts provide the content the public consumes - but it's the same data. A common CMS just makes sense.

    Attachments Open full size
  • Keith Greywood commented
    February 01, 2022 14:18

    Upvote, would be useful for me too

    Attachments Open full size
  • SH commented
    November 16, 2020 10:15

    It's not about the pricing, i don't really care if we pay for 2 websites, I just need to have one shared CMS for both sites.

    Attachments Open full size
  • SH commented
    November 16, 2020 10:14

    We have 2 brands that cross-promote each other. I need the same database in both of them so basically the only viable option right now is to have my team do the same updates in the CMS two times which is just dumb.

    Attachments Open full size
  • Ben Gilbert commented
    August 01, 2020 22:27

    This would be huge! My use case is that I'd like to start working on a new site based on my same CMS data, but I won't be ready to deploy the new site for a month or two and will need to keep adding new elements to my CMS between now and then. I'd like both the current site and the draft of the new site to work off the live data.

    Attachments Open full size
  • Piotr Bagniewski commented
    July 26, 2020 20:23

    upvote

    Attachments Open full size
  • Meredith Knight commented
    August 29, 2019 18:01

    This is becoming a critical issue for us.  Would REALLY love to see this.

    Attachments Open full size
  • Luke Bishop commented
    February 20, 2019 18:09

    Personally, I would love to see this so I can push the same content to different subdomains.

    Attachments Open full size
  • Shane commented
    August 14, 2018 07:25

    For me personally, it would allow me to lower the API processing/requests that essentially update multiple duplicating CMS's across multiple projects/sites.

    I envision using the 10,000 items for each of my 10-15 business projects/sites.  I'm having to use a third-party DB to centralise the data, before pushing updates to the various sites.

    Looks to be the only way forward for efficient multi-site collection/data management.

    I also believe you may run into more of a demand when the eCommerce version of WebFlow is released.

    Attachments Open full size
  • +61

Related ideas