True, the Modern homepage and Modern Site Pages do have a slighty different design, which can be a little jarring when navigating around. With the homepage in mind I guess we have the extra space allowing for the focus to fall on Team News.At Ignite 2016 it was mentiond that customisation options for the banner on non-homepage Modern Site Pages would be coming in the future. Unfortunately I don't remember the session ID it was mentioned in.Hopefully this is something that will come once everything has received at least the first pass of the 'Modern SharePoint' look and feel.

• Sharepoint Online Powershell Get List
• Powershell Sharepoint Online List

Is there an official post covering the excessive white space in header area. We just started using modern pages across some sites (where the majority are still using pre-defined templates via a governed provisioning process), and users are not happy about this extra white space (complaining about having to scroll unnecessarily).

In effect, it's now tagged as a productivity issue, and as a result, we are relunctant to move forward with it.Seems the white space isn't as priminat on the mobile experience, which is great. Wondering why the UI/UX team chose to do this.Bottom line. How do we get this fixed?

I'll post my own workaround, too. I discovered this one while trying to 'convert' some sites from classic to modern. I wanted them to have a page with the homepage layout that doesn't have any banner.First, go to the Site Pages library and download any of the modern pages. Next, open SP Designer, open Site Pages, then create a new ASPX and edit it in Advanced Mode.Open up the page you downloaded into a text editor, such as Notepad, and copy everything.

Back in Designer, replace the default ASPX code with your modern page code you just copied. I have the new editing features on my dev tenant but they have not made it to my employers tenant just yet.These are great features, love the new column templates and the ability to change the header imageBut! Modern pages are still unusable for my employer.There is no way to scale the header image, therefore your images are set to fit the space and this destroys the resolution, hope this is changed before the final release.We still need the ability to either remove the header and shrink the white space, you can choose to not have an image but it still leaves a big gap between the Page Title and the Page Body.Users do not like a lot of white space between these elements. We would like to remove the title area altogether to be able to make pages appear like the home pages for modern team and communication sites - where content starts right at the top - no title, image, or whitespace. One thing this would help with is setting up a modern homepage for existing sites. The guidance to create a new modern page, set it up with web parts, and set as homepage leaves you with a site that looks quite a bit different than a brand new Office 365 Group site which does not have any kind of title header on the landing page.I'm also interested to know where to find out more regarding first release for minor items.

For example - I have two accounts in the same tenant - one on first release and the other not. At first, the one could create a Communication Site, and the other could go there and see it, but the layout was garbled. As of today, the account not on first release can see the page with the layout looking much better - however the options for the Quick Links web part are different between the two accounts (new compact view along with filmstrip for first release) and the editing experience looks slightly different (this is true on Team Sites for which both accounts are owners as well).

What does the roll-out path for minor changes like that look like? In my case, I was not so much interested in removing the page title than just removing the excessive dead space on the top of the page. I noticed the same issue when I made forms with Infopath that drove me nuts.I'm not against, white space, but it was just over the top too large.I suspect your visual developers are not using the screen resolution that the average office worker is using. I am sure the existing white page looks fine on a very high res monitor How about making the white space responsive to the resolution of the monitor so it looks fine everywhere. The amount of white space is definitely an issue, but as this has been addressed somewhat the next pressing issue for me is the default behavior of the Quick Launch links. By default, the tree is shown in expanded view, meaning a lot of the root subsites are not shown, and instead have to be found by collapsing the subsites in view, or by scrolling. New users to SharePoint are not immediately familiar with this practice, nor in my opinion should they have to use additional clicks/time to collapse subsites in their way to display the actual subsites they wish to navigate to.

Please allow a default value to have lists collapsed as default! Hi Alyssa,This morning I see that the white space is greatly reduced in my dev tenant, if I delete the background image, this is great. My employers site does not have this ability yet, but when this is rolled out I think this will be more acceptable to my co-workers.Sorry I was not more clear on the Title region, I was referring more to the white space and background image being so large, but now that the space is reduced, I still have to get feedback from my boss and coworkers but I don't see this as big an issue for us anymore.Thank you.

SharePoint Online column formatting was announced at Ignite and is now available in production. The column formatting feature allows SharePoint site owners to control the display of fields in a SharePoint view including conditional formatting, applying formatting based on a date range, creating clickable actions, some visualizations (such as a status bar), and the use of some pre-defined icons.At a high level here are some of the advantages and disadvantages of the current column formatting functionality.Advantages. JSON is a very well supported industry standard format in the enterprise developer space.

Many tools and text editors provide support for this format. Has features which can replace some or all of the view customization that was previously available in SharePoint designer. Achieves custom field display and keeps SharePoint out of the box. Works with modern lists and libraries.Disadvantages. No custom code. Developers looking for a more high end solution with custom code would want to look at the SharePoint Framework Field Customizer extensions. I can see some potential governance issues.

It’s similar to the script editor web part – all site owners have access to use it. JSON and CSS are not ‘user friendly’ by any means. Doesn’t work in SharePoint ‘classic’ mode.For my example, I will add column formatting to an out of the box SharePoint custom list to highlight a couple different status values. I will be providing the steps to create this solution, for a more detailed walkthrough of how column formatting works and how you can create your own solutions, see the Microsoft article in the reference section.1.

Sharepoint Online Powershell Get List

Add a new custom list to your SharePoint site. From the settings menu (gear icon) click the ‘add an app’ menu item.Then select the custom list app.You can provide a name for the tasks list such as ‘List with Formatting’, then click the ‘create’ button.2.Add a Status column with formatting. After the last step your screen should be open to the site contents screen. Open the task list by clicking the link for the list from the site contents screen.Then with the list open click the settings menu and the List Settings menu item.Scroll down to the columns section and click the ‘create column’ link.Next, for the column name, type in Status. For the type select choice.Next add two choice values: ‘No Issues’ and ‘Requires Attention’.Now scroll down to the bottom of the screen. You will see a new textbox that allows us to put in the column formatting.Below I have a listing of the JSON for the formatting we will use. Copy this text and paste it into the column formatting box shown above.

Finally click the ‘ok’ button to save the new column with its formatting.3.Add some test data and view the results. Add 2 new items – set the status to ‘No Issues’ for the first one and ‘Requires Attention’ for the second one.After the two items are added, lets see how it looks.From the role of an enterprise developer or system administrator, I would like this feature.

JSON and CSS classes are very mainstream skills for modern web developers. The ability to add column formatting to a list or library without the need to create a complete app or SharePoint framework solution is appealing.From the perspective of a regular site owner, I would be frustrated with this feature. All site owners would have access to the column formatting, but setting up column formatting, especially the more complex scenarios gets technical very quickly. Even for the example in this post, I needed to utilize VS Code so I could match up all of the opening and closing brackets and parenthesis. I think this level of complexity puts this feature out of the reach of most site owners outside of the IT / Developer areas.From the role of someone who sets SharePoint governance, this feature may be a source of problems.

Administrators currently don’t have the ability to deactivate this feature. For many organizations, this would be a nice feature for administrators and developers but would be something I would want to restrict for regular site owners.

Powershell Sharepoint Online List

At a minimum from a governance perspective you would need to set a direction on this feature – can site owners use this feature on their own or should it only be used by the administrators and developers supporting SharePoint for their organization.My final verdict is a bit mixed, I like what we can do with this feature, especially for technical people such as IT pros and developers. But JSON and CSS is not something accessible to most site owners, and the lack of controls to restrict who can do column formatting does create a potential governance issue.I would like to see this feature mature a bit further.

Additional controls as to who can do column formatting (governance controls) and some more user-friendly wizards for regular site owners. Something similar to conditional formatting in Excel that saves the JSON behind the scenes would be a great addition.Use Column Formatting to Customize SharePoint.