Today is the official launch day for SharePoint 2010. As a consumer, you can finally get your hands on this product without merely reading about how this is the best web-based product ever conceived. No longer will you have to rely on my prediction that SharePoint 2010 will ultimately force you to coddle your server while mumbling “my precious”.

Okay so I’m being a bit dramatic here, but don’t say that I didn’t warn you. If you’re still looking for a reason to install this thing, then let me introduce you to a few really cool features that you may not know about in SharePoint 2010.

1. Wiki-like WYSIWYG Editor For Site Pages

Editing is not fun. In fact, it can be downright annoying. And this is especially true in a web browser. Not only do we have to continually fight with our editing tool to get it to do what we want, but many times it doesn’t have the capabilities we need to make us more efficient. This is one huge improvement to the SharePoint platform that will aim to fix this problem. The editor is completely rendered in AJAX, and it is wiki-like in its execution.

You can make changes on the fly like you’re in Word, and you can quickly create/link to other pages and content by typing “[[new page]]” without the quotes. If the page doesn’t exist, then you’ll be able to create it on the fly when you click on the link. You don’t have to stop your thought process to address technical barriers.

SP2010_pagelinking.jpg
Page Linking in SharePoint 2010

Linking to list items and documents is just as easy. Simply start typing the double brackets and you’ll get a listing of available items to link to. For documents, just type in the path to where the document lives on the server, and it will be live once you save the page.

SP2010_listlinking.JPG
List Linking in SharePoint 2010

2. Quickly Change Chrome Languages On The Fly

There have been some nice improvements to the multilingual capabilities in SharePoint 2010. One of these is the ability to change the language of the chrome with a few mouse clicks. This effects everything but your content -- which still needs to be localized by adding translations into the resource files.