Currently, unlike version 6, the 365 solution does not support page duplication in the CMS editor. We encountered the first customer needing it and we think it is a generally useful feature to have.
This is an intended change. There is no "copy link content" in 365 CMS as this led to very unstructured, messy and hard to figure out, hard to change and hard to fix site configurations. This functionality has been replaced by a much more organised and useful tool which is called "Content Sets". having ,migrated your site from v6 there wont be any content sets. It'll take a bit of effort but well worth doing. If you find your most commonly used "sets of content" (i.e. the old pages you most commonly copied) and create contents sets for this set of content, you will then find it easy to apply this content to a new page, and much easier to maintain going forwards.
I just realised this is not possible in 365 :-( Thankfully i do not need to create new pages often, but when i do it's going to be time consuming. If the linking of content placeholders worked more smoothly, the pain would be less but that action of linking a placeholder to an existing page is clunky
This is an intended change. There is no "copy link content" in 365 CMS as this led to very unstructured, messy and hard to figure out, hard to change and hard to fix site configurations. This functionality has been replaced by a much more organised and useful tool which is called "Content Sets". having ,migrated your site from v6 there wont be any content sets. It'll take a bit of effort but well worth doing. If you find your most commonly used "sets of content" (i.e. the old pages you most commonly copied) and create contents sets for this set of content, you will then find it easy to apply this content to a new page, and much easier to maintain going forwards.
I just realised this is not possible in 365 :-( Thankfully i do not need to create new pages often, but when i do it's going to be time consuming. If the linking of content placeholders worked more smoothly, the pain would be less but that action of linking a placeholder to an existing page is clunky