When I was learning basic networking back in the late 90's, I was introduced to a fun, yet insightful RFC that contained the 12 Fundamental Truths of Networking (RFC 1925). In this post, I'd like to correlate those truths with SharePoint. The truths were meant to be a bit tongue-in-cheek, but they are useful when thinking about a SharePoint deployment.
This week, I found out a very interesting fact: there is a limit to the number of Web Parts a page can have in SharePoint 2013. I know what you are thinking: How on Earth did someone find out there was a limit to Web Parts on a page in SharePoint. Or if you were me, it was, "Holy smokes that is crazy, but interesting!"
SharePoint Online presents quite a compelling business case for most organizations. It offers a tremendous amount of features for a low cost and fewer headaches. However, many companies still need to keep an on-premises SharePoint farm for a variety of reasons, requiring them to deploy a hybrid topology.
Many times we want to give someone a quick status by stopping by their office and saying a quick sentence. I'm the recipient of this type of drive-by status quite often. Usually it happens by people standing in my doorway and starting to talk.
If you have a use for the blog site template, you've seen the OOTB experience provided by Microsoft. While useful, it has its short comings. I recently had the opportunity to take a look at customizing the view of a blog on O365 and I thought that this may help someone out there.
As I'm sure you know, Office 365 is a pretty incredible product. Honestly, Microsoft has knocked it out of the park with the platform. It really is impressive what they have accomplished, and it's pretty wild to think that we're still pretty early in the product's lifecycle. Every business really should be seriously considering how they can be taking advantage of Office 365's rich offerings.