PnP-Provisioning-Schema icon indicating copy to clipboard operation
PnP-Provisioning-Schema copied to clipboard

Ability to provision Publishing Pages w/ web parts in zones.

Open brianpmccullough opened this issue 8 years ago • 3 comments

I understand publishing functionality is going to be deprecated, but there are probably lots of On Prem customers who have intranets/portals built on the publishing infrastructure. For these customers there should be a model for provisioning publishing pages into the "Pages" library with ability to specify Web Parts in zones.

Some candidates for functionality:

  • Ability to specify the Content Type and Page Layout during provisioning.

  • Ability to specify the field values (including Page Body Text, Title, Contact, and any custom field values)

  • Ability to specify how the provisioning engine should treat each existing pages by same path (Replace, Overwrite, DontModify, AddMissingWebParts, DeleteMissingWebParts, etc)

  • Ability to specify what we want to do in the event the page is already checked out (OverwriteCheckout, NoModification)

  • Ability to specify if the engine should checkin and/or publish the file upon completion (and allow for checkin comments)

  • Ability to specify what the engine should do if it cannot complete the provisioning of a given page (Warn, Abort).

brianpmccullough avatar Dec 20 '16 19:12 brianpmccullough

thx brianpmccullough, we'll absolutely take this into account around the new version schema design. There are thousands and thousands publishing sites also in the SharePoint Online, so the request is absolutely valid cross different versions.

VesaJuvonen avatar Jan 31 '17 11:01 VesaJuvonen

@VesaJuvonen I'm on 2013 On Premises and Publishing sites is pretty common in our organization. Curious to know why PnP team has not considered support for Publishing pages at the time when they supported for wiki pages through pnp:pages?

VenkateshKadiri66 avatar Apr 22 '17 07:04 VenkateshKadiri66

Hi Venkatesh , PnP is open source, community driven initiative, so the work is highly dependent on the contributions from the community. Obviously engine had to start from somewhere and it was started with a support with team sites, but publishing sites are already supported... except with certain capabilities. Publishing sites are absolutely important and engine will have more and more support for them when we get contributions from the community around missing capabilities.

VesaJuvonen avatar Apr 22 '17 13:04 VesaJuvonen