Skip to main content

Step by Step for create and deploy a SharePoint 2016 Custom Layout With out using designer or Design Manager

This article is a to ensure how to create a simple SharePoint 2016 Page layout without using

  • Share Point designer
  • Design Manager

Before doing anything you need to create the base of the layout.

Following placeholders are minimal and commonly used in any template.

  • PlaceHolderAdditionalPageHead
  • PlaceHolderPageTitle
  • PlaceHolderMain

Place Holders

PlaceHolderAdditionalPageHead

This place holder is used to defined additional CSS and other scripts and inline CSS if you have any.

We will be using this to register a CSS and register a different CSS for the SharePoint Edit Mode

<asp:Content ContentPlaceHolderId="PlaceHolderAdditionalPageHead" runat="server">

<!—Your code goes here-->

</asp:Content>

PlaceHolderPageTitle

This place holder will be mainly for the page title.

<asp:Content ContentPlaceHolderId="PlaceHolderPageTitle" runat="server">

<!—Your code goes here-->

</asp:Content>

PlaceHolderMain

This is the main section for your temple. here you can define web part zones or any other HTML code segments such as Bootstrap or static HTML as you want.

<asp:Content ContentPlaceHolderId="PlaceHolderMain" runat="server">

<!—Your code goes here-->

</asp:Content>

Base Template

Adding standard SharePoint controls, you can make your base template as follows.

<%@ Page Language="C#" Inherits="Microsoft.SharePoint.Publishing.PublishingLayoutPage,Microsoft.SharePoint.Publishing,Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %>

<%@ Register TagPrefix="SharePointWebControls" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register TagPrefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register TagPrefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<asp:Content ContentPlaceHolderId="PlaceHolderAdditionalPageHead" runat="server">

<!-- Styles for edit mode only-->

</asp:Content>

<asp:Content ContentPlaceHolderId="PlaceHolderPageTitle" runat="server">

<!-- Styles for edit mode only-->

</asp:Content>

<asp:Content ContentPlaceHolderId="PlaceHolderMain" runat="server">

<!-- Styles for edit mode only-->

</asp:Content>

Extend your Template

PlaceHolderAdditionalPageHead

First, add general CSS registration to this section

<SharePointWebControls:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/pagelayouts15.css %>" runat="server"/>

Then I'm going to define a CSS for EDIT mode, this will be really needful when you are hiding some tags when not in the Edit Mode.

<PublishingWebControls:EditModePanel runat="server">

<!-- Styles for edit mode only-->

<SharePointWebControls:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/editmode15.css %>"

After="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/pagelayouts15.css %>" runat="server"/>

</PublishingWebControls:EditModePanel>

then you will need to add other scripts or CSS formatting if necessary.

<style type="text/css">

<!-- Styles -->

</style>

<script type="text/javascript">

// your code

</script>

Finally, you will have your AdditionalPageHead as below.

AdditionalPageHead


<asp:Content ContentPlaceHolderId="PlaceHolderAdditionalPageHead" runat="server">

<SharePointWebControls:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/pagelayouts15.css %>" runat="server"/>

<PublishingWebControls:EditModePanel runat="server">

<!-- Styles for edit mode only-->

<SharePointWebControls:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/editmode15.css %>"

After="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/pagelayouts15.css %>" runat="server"/>

</PublishingWebControls:EditModePanel>

<style type="text/css">

<!-- Styles -->

</style>

<script type="text/javascript">

// your code

</script>

</asp:Content>

PlaceHolderPageTitle

just adding the SharePoint Page Title here.

<asp:Content ContentPlaceHolderId="PlaceHolderPageTitle" runat="server">

<SharePointWebControls:FieldValue FieldName="Title" runat="server"/> 

</asp:Content>

PlaceHolderMain

Here goes with one web part zone for simplicity.

<asp:Content ContentPlaceHolderId="PlaceHolderMain" runat="server">

<WebPartPages:WebPartZone runat="server" Title="Top Left" ID="TopLeftZone"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone>

</asp:Content>

Final Template

<%@ Page Language="C#" Inherits="Microsoft.SharePoint.Publishing.PublishingLayoutPage,Microsoft.SharePoint.Publishing,Version=15.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %>

<%@ Register TagPrefix="SharePointWebControls" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register TagPrefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<%@ Register TagPrefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

<asp:Content ContentPlaceHolderId="PlaceHolderAdditionalPageHead" runat="server">

<SharePointWebControls:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/pagelayouts15.css %>" runat="server"/>

<PublishingWebControls:EditModePanel runat="server">

<!-- Styles for edit mode only-->

<SharePointWebControls:CssRegistration name="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/editmode15.css %>"

After="<% $SPUrl:~sitecollection/Style Library/~language/Themable/Core Styles/pagelayouts15.css %>" runat="server"/>

</PublishingWebControls:EditModePanel>

<style type="text/css">

<!-- Styles -->

</style>

<script type="text/javascript">

// your code

</script>

</asp:Content>

<asp:Content ContentPlaceHolderId="PlaceHolderPageTitle" runat="server">

<SharePointWebControls:FieldValue FieldName="Title" runat="server"/> 

</asp:Content>

<asp:Content ContentPlaceHolderId="PlaceHolderMain" runat="server">

<WebPartPages:WebPartZone runat="server" Title="Top Left" ID="TopLeftZone"><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone>

</asp:Content>


Copy this template to a file samplepage.aspx


Upload the Content Template

First, Navigate to Site Settings

Then find the Web Designer Galleries and go to Mater Pages and page Layouts

Then Upload document and choose the file that you have saved previously.

Then, You need to choose correct content Type.

It should be PageLayout and you can Map with any Content Type.  For an Example, I will be mapped with Article Page.

After that, Save the page and don’ forget to publish the page.

Now we are ready to use the new page layout.

go to the Pages Library and try to create a New Page. You will see your content type listed there.

Labels:

Comments

Post a Comment

Popular posts from this blog

Complete guide to Install SharePoint in a Three Server Farm using AutpSPInstaller

This article will be divided to three sections Setting up the Environment and Service Accounts Getting Ready with AutoSPInstaller Online Configuring the XML using Online Editor and Installation Setting up the Environment and Service Accounts AutoSPInstaller Online is one of a great project that facilitate Automated SharePoint installation including Sharepoint 2010, 2013 and 2016. Auto SP Installer provides a powerful way to deploy and configure a single-server development environment to multiple-server SharePoint farm. Reference: https://autospinstaller.com/ Before doing anything we will set up the environment for SharePoint three server Farm. Will name these servers as SPWFE - Share Point Front End Server SPAPP - Share Point App server SPDB - DB server Please find the reference for SharePoint minimum requirement and practices from https://docs.microsoft.com/en-us/SharePoint/install/install-sharepoint-server-2016-across-multiple-servers For the the medium segregation, we have to create...
Post a Comment
Read more

How to Customize New Item Form to take parameters from Query String in the SharePoint 2010

In here I'm going to explain how to customize the SharePoint Item From to take parameters from Query String and set them as default values using SharePoint designer. Using this you can open a new Item From by providing parameters as query string. For an example you can customize one item Display form and taking query String Parameter from that and view New Item view for another list by providing default values using the Query String.     Steps Open the SharePoint designer and go to list and libraries and open the list that you want. Click the New and create a New Insert View by providing the name of the view.   Then created one will come to the list. then click and open the view. Then default New Item Screen will be loaded as follows. Then Delete the default list view and make that empty. You can delete the controls by selecting the area in the design view, If it fully cleared you can view the following message from the designer. Then go to SharePoint...
6 comments
Read more

Motion Eye Docker compose File

Docker compose files are comes in handy when considering container orchestration. Below example shows my docker compose files and folder structure. ---- Your Folder (motioneye)   -- etc   -- lib   -- docker-compose.yaml You can run the docker compose file using docker-compose -d , and etc and lib folder will be automatically populated in the initiation. --- Below shows the content of the docker-compose.yaml file. version: '3' services:   nodered:    image: "ccrisan/motioneye:master-amd64"    container_name: motioneye    restart: always    user: root    ports:      - 8765:8765    volumes:      - "/etc/localtime:/etc/localtime:ro"      - "./etc:/etc/motioneye"      - "./lib:/var/lib/motioneye"
Post a Comment
Read more