InfoWorker Solutions

Responsive design combined with dynamic user-driven content and mobile first seems to be the main focus everywhere these days. The approach ...

A SharePoint content database can be up to 4TB with data (max 200GB is recommended). However, storage size is not the problem; it is ...

Over the years, I've written quite a few articles on how to technically structure your SharePoint solutions into web-apps, sites, subsi...

I often get asked "how many document libraries and sites will we need?" in SharePoint, followed by "how will we know whether ...

At every SharePoint customer and in every SharePoint project, the issue of how to realize a future-proof, working site structure arise. I...

This post describes a proposed solution design for providing an intranet collaboration farm capable to scale out to support a publishing por...

This is part III in a mini-series about the Minimal SharePoint Governance Plan needed to get you started with your SharePoint governance ef...

This is part II in a mini-series about the Minimal SharePoint Governance Plan needed to get you started with your SharePoint governance ef...

As part of my work doing SharePoint architecture & design at different Puzzlepart customers, the governance aspect always comes up. Eve...

A taxonomy is realized in SharePoint using content types for information asset types and term sets for coherent tagging of information. Con...

In my last post, I presented a SharePoint site classification & structuring scheme for realizing the information architecture (IA) stru...

As part of my work as a SharePoint architect, I almost always run into poorly designed and structured SharePoint solutions. Mostly because c...

Lately I've been reading Building the SharePoint User Experience by fellow Norwegian Bjørn Furuknap , and it is an easy read even if it...