Windows Live Writer Integration for Sitecore

Windows Live Writer is a great tool for blogging. It is simple, fast, and can be customized using plugins written in .NET. You can have web-based interface for adding your blog or articles, but integration with desktop client will not be superfluous as it provides a lot of benefits.
 In this post I'll show how to integrate it with Sitecore CMS using MetaWeblog API -  an application interface  that enables weblog entries to be written, edited, and deleted using web services.

Integration can be divided into two parts:

1. Implementing MetaWeblog API service members 
2. Creating and configuring various handlers that will tell Live Writer how to find and use our service

Using Coveo with Sitecore. Part 2: Performing a Query

This post is a part of the "Using Coveo with Sitecore" series.

• Indexing Sitecore items
• Performing a Query (this post)
• Tips and Tricks (snippets, hidden features and real-world examples)

There are many ways to retrieve data from Coveo, I'll describe most popular of them, their proc and cons.

Integrating search interface "as is"
Such integration of Coveo can be implemented in a day or even less, including configuring Sitecore Connector which will crawl only changed / newly created items, adding and configuring front-end search.

In order to add search interface to your website you need to:

Translating Sitecore items using Google Translate

One of the strongest techniques which can be used to increase sales and get more potential customers of the people from other regions is a multilingual website. Multi-language management is a cornerstone of Sitecore CMS, integrated into all aspects of content and site management. It allows you to build a multi-language website with almost the same effort as a single-language. See this amazing case-study about building website in 28 languages.

But what if you want to translate an existing site with a thousands of pages, hundreds of templates and website sections? How to identify possible architecture(like "Shared" fields that actually should be translated) problems, or implementation bugs (hard-coded texts, displaying item name instead of a title and so on). Sure, you can ask content-editors to spend few weeks in order to translate the site, test it, etc. But how about instant website translation using some online service? Translation quality is not as important when you simply need to identify possible problems after translation, so... let's start!

In this example, I'll use Google Translate as a translation provider. I also tried Bing Translator service, it's almost identical, but does not provide easy API like google-api-for-dotnet.

Tag Cloud from Sitecore content

Let's assume you have a Sitecore site containing "Products" section, it is well-structured by categories, and contains many thousands of items.



Some day you decide to add tags to all your products...

No problem, you should just find a place to store tags



And then add a new field to the product template



Here what you got on each product:


Now the most interesting part, we need to build a tag cloud based on these values. There are lot of ways to implement it, but when you have to deal with really big content tree, the most suitable solution is using some search engine. In this example I'll use Coveo, but it's possible to implement the same functionality using Lucene with almost the same effort.