Recently the user interface to create site collections in SharePoint Online have been updated. The storage quota unit is now gigabytes instead of megabytes. So be careful not to set a storage quota of 1024 gigabytes instead of megabytes. Let’s take a look why this happened.
Changed interface of storage quota
To take a look in the past you can check the official documentation on “How to set storage quota“. Beside this change on the limitation the calculation to evaluate the storage limits has been changed too. This new feature is called pooled storage.
Over the last year I did more branding projects on Office 365 than on on-premise. Since the first call by Microsoft to avoid modifications of the master page I played around with certain scenarios and patterns to reduce or avoid such modifications.
One common issue is that the suite bar is responsive (everything that resize is responsive) but not well optimized for mobile. Without any enhancements this part of SharePoint shows only half of the content. With some small CSS only modifications the suite bar looks great on nearly any device.
The following blog post use SASS pre-processed CSS the compiled CSS can be found too at the end of this post.
If you like to create a responsive user experience it is common practice to add a <meta name=”viewport”> tag to the html. This tag contains instructions to the browser in the matter of viewpoints and zooming and make sure that your web design is scaled properly according to your style definitions. Without this tag SharePoint on an iPhone will look as seen on the screenshot below. Currently SharePoint doesn’t support it by default.
In the first blog post I explained how to set up your Yeoman development environment. You have now a local web server and you can start your web development. Now lets take a closer look how you can integrate the files on this web serve directly into SharePoint on-premises and Office 365.
Open your project and start the web serve with the command ‘grunt serve’.
In my session at the SPS Antwerp I showed the attendees how my personal branding workflow evolved over the past two years. For the demos all I needed was my web browser and Yeoman.IO.
I presented all of my stuff on the ancient looking MacOS armed with SharePoint virtual machines and in Office 365.
It works great for my for Office 365 development as for SharePoint On-premises. No more deployments during development just use it.
I use the resources out of Yeoman such as JavavScript and CSS files directly out of it. Just as we use things from a CDN such as jQuery. Before I can dig deeper on how to use it the first thing to do is to get your development environment ready.
Last Saturday I had the great opportunity to speak at the SharePoint Point Saturday Belgium in Antwerp. It was my first public speaking, I ever did. First, I like to thank the whole SPS Belgium team to make this happen. It was a great event at the ALM. It was a beautiful location.
A couple of weeks I was contacted via twitter about my blog post that shows how to bind JSLink override to certain web parts only. Jared Matfess (@jaredmatfess) tried my script and recognized that somehow the paging of the web part was broken. I dug deeper into this issue and found the cause of the problem. It seemed that the way how I showed the View ID was the origin.
During the last years I’ve intensively used web fonts. Since I published the first blog post on how you use web fonts in SharePoint 2010.
While I just downloaded the web fonts and used the CSS that was included in the font packages I recognized more and more that most of the available web fonts are wrong defined inside the font packages. There are a couple of problems with the definitions of the @fontface that you can avoid creating a cleaner style sheet.
My session is about SASS and how it fits into your modern SharePoint branding and development approach. The session is entitled “Stop your SharePoint CSS become a di-SASS-ter today!” and covers the following key takeaways.
– I will explain what SASS is and where you would use it.
– How to use SASS to brand SharePoint without requiring lengthy deployments.
– How to create simple Rich Text Editor Styles using mixins and includes.
– How to apply a Grid layout and make it Responsive.
– How to structure your branding correctly to make it more maintainable.
– How CSS 4 fits into the picture and does it make SASS obsolete?
See you in Antwerp, 18th April 2015!!!
SPChat – Branding Office 365 and SASS
About one month before my session in Antwerp, on 19th of March, I will be available to for an SPChat on Branding Office 365 using SASS.
You are gladly welcome to open discussion on how to get started using SASS. Get to know some cutting edge extensions that you should take a look into and talking about the challenges in Office 365 when it comes to enhance the user experience.
You will find more information at SharePoint-Community.net