SharePoint Modern Sites

-
In 2016, MS announced a revolutionary change in SharePoint, the change which was capable enough to attract people towards SP, the change which was very lightweight and easy to provision, the change which was mobile first, the change which was for the more open source rather than traditional server-side scripting. And the change was, MS came up with a new concept i.e. MODERN SITES.

The very next thing which came in everyone’s mind, how these modern sites are different from classic SharePoint sites. Apart from above mentioned, here is a couple of difference which would make sense why.

SharePoint Modern sites are “NoScript” enabled, that means there are few operations which can’t be possible when “NoScript” is enabled, like Cannot save site/Library as a template, Solution Gallery/Theme Gallery/Help Settings/Sandbox solutions not available in site settings, etc.

Whenever modern sites are created, by default they are having awesome look and feel, and this new UI supports most of the browsers as well as mobiles and tablets. At the same point in time, this is very lightweight so loading of the pages is also very smooth. This is another significant difference in comparison with classic sites.

Figure#1: Desktop View


                                                               Figure#2: Mobile View

Next thing, How Modern Sites can be created, whereas it is not available in SharePoint admin center?
SharePoint team provided separate option to create Modern Sites and that option can be explored by following below link.
https://TENANT.sharepoint.com/_layouts/15/sharepoint.aspx

Figure#3: Create Modern Sites
As per the above figure, Modern sites can be created. As of now, MS introduced two Modern Sites.
1.       Team site
2.       Communication site
Team Sites were already there in Classic Sites, then what is the difference b/w these two?
Apart from UI, look n feel etc., there is one substantial difference and i.e. when Modern Team Site is created, automatically it will create a relevant O365 group and vice versa. Here the benefit is, users in the O365 group will be having permission on team site.  You do not need to go to the site and provide access there, which saves efforts, time and inconvenience.

Communication sites are best to reach your audience, it is faster, rich, dynamic and more expressive. For example, if there is an announcement, product launch, events, status update, news etc. simply you can create a page and in that page, you can embed images, videos, BI analytics, Yammer discussion etc. and that page will be vibrant, interactive, mobile ready and far beyond than email communication, with rich UI.

Or else you can use existing templates in Communication site. Those are Topic, Showcase, and Blank.



With the help of above three templates, you can get your site designed as per your requirement.


Comments

Post a Comment

Popular posts from this blog

C# Copy files from one server to another

-
Sometimes we need to copy files from one sever and paste those files to another server programmatically. So for that we can use below code but we should have admin credentials of that server where we want to paste files. In below method we need to pass source path of the server, from where we want to copy and destination path of the server, where we want to paste. Also we need to provide UserName, Domain, Password of the server where we want to paste those files. public void CopyFiles(string sourcePath, string destinationPath)         {             try             {                  IntPtr admin_token = new IntPtr();                 // use LOGON32_LOGON_NEW_CREDENTIALS as LogonType                 if (LogonUser(" UserName ", " Domain ", " Password ", 9, 0, ref admin_token) != 0)                 {                     WindowsIdentity wid_admin = new WindowsIdentity(admin_token);                     WindowsImpersonationContext wic =
Read more

Export SharePoint Online Group Users to Excel using Powershell

-
Sometimes, we have a requirement to generate user reports from SharePoint groups or validate which user is added to which groups etc. If we do this activity manually, it may take forever (obviously based on the user added to group 😉).  Classic example, recently in my project i got a requirement where i need to find all the users who are added to multiple SharePoint groups. Now i have 2500 users added to my SP Groups and it is difficult to check one by one. So i generated CSV/Excel for each group and added a vlookup in excel and got my report. Below is the Powershell script, which helps to generate CSV file based on group name.  Note: All the input variables are mentioned in Green Color, Please update before executing this script. $aClient = [ System.Reflection.Assembly ]:: LoadWithPartialName( "Microsoft.SharePoint.Client" ) $aClientRuntime = [ System.Reflection.Assembly ]:: LoadWithPartialName( "Microsoft.SharePoint.Client.Runtime" )   Function Get-UserInfo
Read more

Suppress StyleCop SA1600

-
    Local Suppression: [SuppressMessage("Microsoft.StyleCop.CSharp.DocumentationRules",  "SA1600:ElementsMustBeDocumented", Justification = "Reviewed.  Suppression is OK here.")] for local suppression you must use namespace  using System.Diagnostics.CodeAnalysis;   OR you can also use   [System.Diagnostics.CodeAnalysis.SuppressMessage ("Microsoft.StyleCop.CSharp.DocumentationRules", "SA1600:ElementsMustBeDocumented")]  Example:   using System.Diagnostics.CodeAnalysis;   [SuppressMessage("Microsoft.StyleCop.CSharp.DocumentationRules", "SA1600:ElementsMustBeDocumented", Justification = "Reviewed. Suppression is OK here.")] protected void Button1_Click(object sender, EventArgs e)   {   } [SuppressMessage("Microsoft.StyleCop.CSharp.DocumentationRules", "SA1600:ElementsMustBeDocumented", Justification = "Reviewed. Suppression is OK here.")]  protected v
Read more