So you decided that your company could benefit from an intranet. Or maybe you found that the existing intranet doesn’t fit modern day’s requirements. You convinced your manager or CxO and in doing so you found yourself a project sponsor. So basically you’re about to start up an intranet project. First things first, so you want to define your business requirements or revise the existing ones that were used to conceptualize the existing intranet years ago. Most likely, you fire up Excel and start collecting Must Haves, Should Haves, Could Have and Would Haves. On the side you draw some sketchy wireframes in PowerPoint. Alternatively you may be using Visio or Balsamiq. Once you’re done, you have a look at the company’s list of IT suppliers and agencies. Three of them you send your functional specification and request a proposal. All three of them respond within four weeks by sending you their quote for realizing your intranet the way you want it. You notice that all three of them propose using Microsoft SharePoint 2010 Server. That makes live a lot easier when it comes to comparing those three proposals. You also notice that all three of them sent you a rather hefty document with a lot of emphasis on producing a concept. And this is where you start to ponder. Haven’t all three companies before produced intranets for different clients? Are your requirements so much different than any requirements they’ve come across before? The more you think about it, the more you are convinced that there must be another way. Factory … IntranetFactory! Isn’t there such a thing as an IntranetFactory?
Yes, there is. Surprisingly enough, it’s actually called the IntranetFactory. It basically incorporates a lot of knowledge that has been accumulated over the years by intranet experts. This expertise has been ported to the SharePoint Intranet Modeler. It is a unique tool for rapid and interactive prototyping of a SharePoint site independently from its real implementation. Even better, you don’t need to install anything. It’s simply available for everyone as a free service in the cloud. Once you’ve registered and logged on, you can access the Modeler via your browser. On the landing page you’ll find your own model, models provided by the IntranetFactory team and models shared by others. To get started, you simply copy an existing model. I decided to copy the sample model provided and used that to create my own template. Curious as I am, I immediately clicked “view wireframe”.
(Click image to enlarge)
When I moved my mouse over the various placeholders for web parts, a comment popped up with a brief description of that particular web part. Somehow I immediately loved it and just wanted to add my own web parts, delete existing ones and just simply play around with it. I was hooked. I closed the wireframe and on the Modeler’s landing page clicked “edit model”.
(Click image to enlarge)
In the left panel I noticed a “Content & Applications” and “Sites & Pages” section. I decide to drag a new page from the panel onto the tree structure shown in the main window. I quickly went back to the wireframe to discover that the new page was now visible in my wireframe. This was easy! Still I didn’t know how to add web parts to the page. In the main window, I clicked the page I just added and in the toolbar the “Edit Content” button became enabled.
(Click image to enlarge)
The screen was reloaded and now I could drag web parts from the left panel onto my new page shown in the main window. Life was never easier before! I became cocky and decided to delete all pages from the sample model I copied and started from scratch with my own model.
(Click image to enlarge)
I simply created a landing page and a couple of blogs and sites below it. In a real world, I would not have stopped here. But for now, 5 minutes down the line, I was happy with the result. I could see how this tool would substitute all my hard work drawing wireframes using Visio or Balsamiq. Still, I didn’t feel made redundant … yet. I could also imagine how I would take this sketch and show it to customers. Actually, working with the SharePoint Intranet Modeler is so dead easy that they can work with it themselves.
But the product is called IntranetFactory for a reason. In addition to the online Modeler, you can download the IntranetFactory. This download actually consists of two components. One is a SharePoint solution that needs to be installed on your SharePoint Farm. The other is the Model Connector. The Model Connector can actually read the model I just created in the cloud and synchronize it with a real SharePoint site. Without going into much detail here, I can say that I was able to install both components without any trouble. It goes without saying that you need to have installation rights or else you can’t add a farm solution to your SharePoint installation, deploy it and activate its features. Synchronizing took only a couple of seconds and when I logged on to my updated SharePoint site, I was really flabbergasted to find my model now alive and kicking.
So am I -a hardworking SharePoint Consultant- now out of work? I guess not. I strongly believe that with the IntranetFactory a company can save itself a lot of time and money to get the first 80% of their requirements realized. And it’s exactly this 80% that is more or less the same for every company. For a SharePoint Consultant this could mean that he can quickly jump to the more interesting bit, namely implementing the remaining 20% requirements.
Of course there are a couple of things to watch. A SharePoint installation needs proper governance from both business and IT. If this sounds new to you, please first read http://sharepointmagazine.net/articles/avoid-newbie-mistakes-10-steps-to-successful-sharepoint-deployments. Part of that is currently covered by the IntranetFactory in that changes to the model can be synchronized down to the real world SharePoint intranet. However, there is more to SharePoint than just lists and libraries. As we all know, everything in SharePoint is a ContentType and this is something I missed in the current version of the IntranetFactory. However, I contacted the team at IntranetFactory.com and they assured me that they are currently working on an extended version that will allow (among other things) for designing SharePoint ContentTypes as well. However, you’ll only need custom ContentTypes if you run into requirements currently not covered either by SharePoint’s out of the box web parts or by IntranetFactory’s own set of web parts called the SharePoint Intranet Suite.
I can really see how the IntranetFactory will save companies time and money whilst giving them a lot of freedom when it comes to shape their intranet over time.
Hey, did I actually mention that I really like the idea of people sharing their wireframes? Good ideas are seldom.
Visit the product page on the SharePoint App Market here: http://www.sharepointappmarket.com/ads/modeler-for-sharepoint-by-intranetfactory/








