I think in this version Microsoft did a very good job, it's amazing what they've done in 3 years, not just in the WCM part but in the entire product. 

About WCM there is a lot of improvements, the new ribbon makes life easier for content producers, for designers it's possible to controls what styles can be used on the RichTextEditor.

Has i said before SharePoint is compliant with WCAG acessibility guidelines http://www.w3.org/TR/WCAG/

Now it's easier to upload pictures to SharePoint, tags that are set in local images are also promoted to SharePoint. It's possible to use wiki pages in public sites with all the look and feel of the public site, and the free structure of the new wiki pages.

The Search Engine Fields  now appears on page in edit mode.

There is a new Asset library and a new Media Player WebPart (Silverlight), now it's possible to streaming videos from the blob cache, the CQW (Content Query WebPart) has some new features like the PageFieldValue where it's possible to filter the content of the CQW using a the value of a field in the page.

A very bit improvement it the possibility to have different host headers for each site collection in one Web Application.

It's now possible to manage a site in any browser (IE, FireFox, Safari)

Now you can export publishing workflows and then reuse them in any site that you want, without the need for creating and filling for each site a new workflow.

The Incremental Content Deployment that gave so many headaches to a lot of SharePoint Administration now is more reliable with a better logging and diagnostics, it's now possible to use Point in time snapshots on SQL Enterprise also with more logging and diagnostics.

The post Web Content Management in SharePoint 2010 appeared first on Blog IT.

<IMG src=”/PublishingImages/picture.GIF” />

When working in context of a page layout, we can easily include image fields by inserting an Image Field control using SharePoint Designer. However, there are situations where we must use the SharePoint Publishing API and there’s where the ImageFieldValue class comes in hand. This class represents an <IMG> tag and its properties. A common situation is when you want to get the Image URL from its HTML markup. This example shows how it can easily be achieved by using the ImageFieldValue class:

public
static
string getImageUrl(string imageFieldHTMLMarkup)

{

Microsoft.SharePoint.Publishing.Fields.ImageFieldValue image =

new Microsoft.SharePoint.Publishing.Fields.ImageFieldValue(imageFieldHTMLMarkup);

return image.ImageUrl;

}

More information about the ImageFieldValue class can be found in the MSDN web site.

UPDATE 01/11/2018:

If you or your customers are not ready to move entirely to the Cloud and Office 365, a hybrid scenario could be an interesting scenario and SharePoint 2019 RTM was recently announced with improved hybrid support! To learn all about SharePoint 2019 and all its features, click here.

UPDATE 21/11/2018:

If you want to know all about the latest SharePoint and Office 365 announcements from Ignite and some more recent announcements, including Microsoft Search, What’s New to Build a Modern Intranet with SharePoint in Office 365, Deeper Integration between Microsoft Teams and SharePoint and the latest news on SharePoint development, click here.

The post SharePoint 2007 – Getting URL from Image Field in WCM Web Sites appeared first on Blog IT.