A blog by Jose Barreto, a member of the File Server team at Microsoft.
All messages posted to this blog are provided "AS IS" with no warranties, and confer no rights.
Information on unreleased products are subject to change without notice.
Dates related to unreleased products are estimates and are subject to change without notice.
The content of this site are personal opinions and might not represent the Microsoft Corporation view.
The information contained in this blog represents my view on the issues discussed as of the date of publication.
You should not consider older, out-of-date posts to reflect my current thoughts and opinions.
© Copyright 2004-2012 by Jose Barreto. All rights reserved.
Follow @josebarreto on Twitter for updates on new blog posts.
Web 2.0 is one of those things everyone is talking about. If you’re implementing Web 2.0 with Microsoft technologies, this usually leads to a SharePoint conversation. Microsoft Office SharePoint Server 2007 (MOSS 2007) includes built-in templates for all the different types of trendy Web 2.0 sites, but which one is the right one for your specific need? Well, that decision is not as easy as it seems.
The main Web 2.0 sites will include Wikis, Blogs, Forms, Surveys and other types custom pages, by themselves or combined into a personal, team, departmental or corporate site. Choosing exactly what fits best to your project will depend on what you’re trying to accomplish. You will need to define the scope of the site. You should also figure out who will create content and who will consume that content. Keep in mind that you might actually need multiple sites, in some sort of hierarchy.
In many cases, you or someone in your group might be experienced with a specific type of site. In that case, it’s common to try to turn every need into that specific type, even if that’s not exactly what it’s designed for. For instance, if you’ve always liked wikis and have a lot of experience with a specific product that was created around the wiki concept, you might want to design every Web 2.0 site as a wiki. This is not unlike the person that knows Excel really well and thinks of every document as an Excel spreadsheet, including proposals, flowcharts, project plans, data entry forms and presentations.
Wikis are usually targeted at scenarios where everyone can change the content. Blogs are usually more restrictive, with a single individual creating post and everyone else allowed only to provide comments. In a survey, everyone can express their opinion, but within a predefined template. A more classic publishing site will allow a select few to write the content and everyone else can only read.
Keep in mind that those are just the typical scenarios. You could certainly have everyone in a team creating entries in a blog and a wiki where just one person can edit the pages. Also remember that the meaning of "everyone" will vary depending of the scope of the site. Speaking of scope, there are typically personal sites, team sites, departmental sites, corporate intranet sites and public web sites. Each one of those lends itself to a specific type of content. Here are some ideas:
SharePoint includes built-in support and templates for most of the different sites I mentioned above and you can also customize it with workflows, custom forms, permissions and more a sophisticated layout than what’s included out-of-the-box. However, the most important decisions are the kinds of interaction and the scope of your site. And please take everything I shared here just as a starting point in your design. The beauty of Web 2.0 sites is that you can create unique combinations that fit your specific scenario.
PingBack from http://feeds.maxblog.eu/item_213417.html