Article
3 comments

Image Renditions available in Modern Team Sites

Yes, you read correctly. The modern team sites got image renditions or at least predefined image formats that will be used by the responsive experience of modern team sites.
Back in the past image renditions was exclusively available in publishing sites only. Well, you were able to use them in team sites too, but the publishing features had to be enabled at site collection level. In addition, classic image renditions might cause negative performance impacts. This was first spotted and documented by Chris O´Brien.
I guess this new feature doesn’t have much to do with the traditional image rendition and you are able to use it in your web part code too. For example, if you like to write a custom image gallery or develop a classic display template.
[Read more]

Article
0 comment

Remove empty dlls from Sandbox Solutions

On July 29 Microsoft announced that they will completely remove of code-base sandboxed solution support in Office 365.
The main problem is that many of those SharePoint solutions just deploy XML based artifacts but no binary code.
Nevertheless I think many of those sandbox solutions deploy an empty dll to Office 365 especially when they are developed in Visual Studio.
This unwanted dll can be simply avoided directly through the correct configuration of your Visual Studio.

[Read more]

Article
2 comments

The new document library in SharePoint is built with…

Not so fast… As announced at the May the 4th event there are a lot of new technologies that come to SharePoint and you can pick your personal flavored framework to enhance the SharePoint.
Some things of the upcoming changes are already available in Office 365. Things like the hidden web parts or the new document library. Time to rip the components of the new document library apart and show you what was used to build it.

TL;DR

The new document libraries are built with the following three core components:

  • React
  • KnockoutJS
  • RequireJS

In addition a React-based implementation of Office UI Fabric will become available together with the new SharePoint Framework.

[Read more]

Article
2 comments

First new SharePoint Framework web parts arrived on Office 365

While I was looking at the new SharePoint site content page I asked myself if more can be found that gives an indication of the upcoming framework and future improvements.
First, I took a look at the source code. Not a big surprise the page was built again using Facebooks ‘React‘ for the user interface and ‘Knockout‘ was used for data binding.
After that I came up with the idea to take a closer look at the web part gallery to see if might some web parts have been deployed to. To my big surprise I found overall five new web parts.

Web Parts of the new SharePoint Framework Extension

Web Parts of the new SharePoint Framework Extension

While some web parts are used to provide tips and trick or how to get started. Two other web parts are more interesting.
The ‘Embed Video Web Part’ and the ‘Embed picture library web part’. I populated them to the gallery and added them to a page in SharePoint. Currently they are deployed, but sadly not working yet. There are no web part specific properties to be configure now and I guess they current won’t load any additional Script or CSS.

New webparts embedded on page

New webparts embedded on page

Embed video web part makes sense to me because this is currently handled by a script embedding web part. A web part that is not responsive without customization.
The embed picture library web part is more interesting because the description states that you can use this to create a fancy new slide show.
In addition to those upcoming web parts it is likely that the new namespace of the additional framework will be ‘Microsoft.SharePoint.SPX‘.

Finally

It is great to see at least a glimpse of the upcoming changes and how the new user interface will be built. Waiting until autumn is still such a long way to go. Especially if you use the same mechanism to customize SharePoint for at least two years now.
Let’s hope it will be released sooner than later. I guess many people love to get their hands on it and provide feedback. Even if it is not rock solid yet.
If you are not so familiar with things like Yeoman, Angular, ReactJS, Handlebars or Knockout, please check out some really great web casts done by the Office PNP team.

Article
0 comment

European SharePoint Conference 2016 Program announced

I’m pretty exited to announce that the program of this European SharePoint Conference is now available. I was asked to be part of European SharePoint Conference team and I joined as program chairman.

European SharePoint Conference Team

European SharePoint Conference Team

Together with Matt Berg (Microsoft), Lieven Iliano (U2U) and Rodrigo Pinto (Blue Infinity) we put an exiting program together. The amount of sessions submitted was overwhelming and it was a really hard desission to pick.

European SharePoint Conference 2016

European SharePoint Conference 2016

See you in Vienna!

Article
2 comments

How to handle table component of Office UI Fabric

In fact the source code of the table component of Office UI Fabric looks a bit weird because it is currently built with <div> elements instead of HTML table elements.
The intention behind such div based tables come from the idea to improve the responsive behavior. This idea behind this is almost more than five years old. A time that marked the beginning of responsive web design. Nowadays this pattern is only hardly used because no matter how you build your tables you always face the same problems.
Yesterday i got the confirmation on GitHub that this pattern is subject to be changed.
Time for me to show how this pattern can be transformed to a normal HTML element and to show some advanced techniques to deal with tables in responsive web designs.

See the Pen Office UI Fabric – Table by Stefan Bauer (@StfBauer) on CodePen.14928

[Read more]

Article
0 comment

The not so responsive new Office 365 suite bar

Many people recently discovered a new enhancement in Office 365 and especially SharePoint. The suite bar is now responsive if “First Release” option on your tenant is activated.

Responsive Office 365 suite bar rendered on mobile device

Responsive Office 365 suite bar rendered on mobile device

The first people that blogged about this responsive improvement were Wesley Hackett and Marc D. Anderson.
The current implementation works well on desktop but not on mobile devices.

Why it doesn’t make your Office 365 / SharePoint responsive?

Actually the current suite bar lacks of one important thing. The viewport meta tag is currently not implemented in SharePoint or Delve. This tag is responsible to render the page correctly. The display of modern devices has a higher pixel density than the normal desktop computer. The viewport meta tag helps the browser to scale web sites properly. Is this html tag missing in the header of the html document the website will be rendered as a desktop version, but everything is tiny and unreadable unless you pinch and zoom.
If you have a new Lumia 950 for example the pixel density is 314 pixels per inch. Desktop monitor in reality has pixel densities beyond 72 pixels per inch but thus the actual base size your browser renders the web site. All CSS values are calculated based on this.

On mobile devices without a proper viewport meta tag the web site will look like the desktop version, but really tiny and therefore unusable.
This brings us back to the new shiny responsive suite bar. A good example when a web site wasn’t tested on a real device. Works perfectly on a desktop browser but not on mobile. Someone might have forgotten to include the view port on the master page. On my phone, SharePoint will be rendered like this.

Suite bar rendered on mobile device

Suite bar rendered on mobile device

As mentioned earlier, it is currently only available for first release subscriptions. So currently nothing to worry about. I hope this will be fixed in the final release and we currently see an early beta version of the suite bar.
Where can the problem be spotted. Simply everywhere in Office 365. Here is a detailed list:

  • Missing viewport meta tag
    • SharePoint
    • Delve
  • With viewport but not responsive design
    • Outlook
    • Calendar

Outlook and Calendar use device detection. Some sort of Device channel to work responsive.
The only first an real native responsive apps are currently Sway and blog post on Delve. Both are equipped with a correct viewport.

Final thoughts

The new suite bar gives a nice outlook on coming up design features. I expect to see more improvement in the near future. Currently, SharePoint in Office 365 and SharePoint 2016 is built upon XHTML 1.0 and not HTML 5. Once the doctype have been converted an all functions work on HTML5 I guess we will see more adoptions to come out faster and more reliable.

From my perspective the new suite bar is a fast shot. I also have concerns about the usability. On mobile the waffle aka app launcher is hidden behind the three dots in the suite bar. To switch between SharePoint and Mail or Calendar users have to tap twice. This forces to learn user a new behavior because the app launcher was one of the essential improvements recently.
On the tablet devices the app launcher is jumping from left to right. This is actually a no-go. User will get confused. A small resize of the window is enough to show this effect. You don’t even have to be on a tablet device.

If you think about to change the master page of SharePoint to make this work. In Office 365 editing the master page is not recommended to do so. I guess this issue will be fixed by Microsoft sooner or later.
In case of a publishing page SEO meta tag injection can be use to add a proper meta tag. For a javascript based solution to add the viewport meta check out the solution provided on OfficeDev Pattern & Practices.

If you have other concerns, feel free to comment on this blog post.

Article
7 comments

Pure CSS Burger Menu

It is summer here in Vienna and nothing tastes better than a home made burger in the evening. The recipe for a burger is pretty simple. Put some self made patty on the grill. Wait a couple of minutes take the meat from the grill and assemble it all together with some additional component, such as cheese, onions and different kind of sauces, in a burger bun.

Jucy Lucies

To build a burger menu in SharePoint is that simple too, and far beyond rocket science. Again, no master page editing is needed to create such menu. To make sure it works on the premises as well as in Office 365.

[Read more]