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

How to Link Two List and Create a combine view in the SharePoint 2010

In this way you can join multiple list together and can create a combine view. for an example assume that you are managing a list for some events. And also you are having a participants in separate list. Thus you want to join the two list and create a composite view. SharePoint 2010 allows you to create this kind of view using  Linked Data Source. in this approach you can create your own custom list in the SharePoint. How to Create a Linked Data source Go to SharePoint designer and  go to the link called data sources. And Click the Linked Data Source button in the ribbon. Then SharePoint designer will prompt following kind of a dialog. In there add two list, that you wan to linked together. I'm adding airline schedule and booking list. those are the two list that i wan to merge. then click next. And it will guide you another screen. it will ask you to select either Merge Merge use to combine list which are having same columns definition. for and example we can say th
32 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

How to get Username , UserID in CAML Query

If you are want to get the userID you can simple use following code. <Where>    <Eq>       <FieldRef Name='userfieldname' />       <Value Type='Integer'>            <UserID Type='Integer' />       </Value>    </Eq> </Where> in here you should declare the UserID variable before it uses. normally If you make a user filter in the SharePoint designer it will automatically create the parameter in parameter binding section in the web part. <ParameterBinding Name="UserID" Location="CAMLVariable" DefaultValue="CurrentUserName"/> But assume you want to filter using a user name and the field is not a persongroup feild and it is just a text field. then you can use following query to archive it. <Where>    <Eq>       <FieldRef Name='userfieldname' />       <Value Type=’Text’>            <UserID Type=’Text’/>       </Value>    </Eq> </Wh
9 comments
Read more