X

Register now for unlimited access to Sitecore resources.


Already have an account? Log in now

*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
X

Request a demo

It’s easy to get started. Sign up for a personalized demo.

*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.
Sitecore Blog: @sitecorejohn blog

Sitecore Shared Source: NewsMover Organizes News Articles

By John West, June 24, 2010 | Rating:  | Comments (1)

Screen shot of tree created by NewsMover

You can use the NewsMover Sitecore Shared Source project with the Sitecore ASP.NET CMS to automatically organize news items into a hierarchy based on release dates. You can adapt this approach to organize any types of items based on any data.

Many CMS solutions allow users to publish any number of news items in a given day. If users created all news under a single parent item, such as /news, performance and usability would suffer as the number of news items increased. If users moved news items as they aged, URLs would change, breaking external links including browser bookmarks and search indexes.

The Sitecore Shared Source NewsMover automatically creates paths and moves news items based on the value of a date field. For example, if a CMS user created a news item under /news on 24 June of 2010, NewsMover would create the path /news/2010/June/24, and move the item to that location.

See Intercepting Item Updates with Sitecore on my old sitecorejohn blog for descriptions of other strategies for intercepting item updates.

Update 24.June.2010NewsMover video demonstration (2MB .mov file).

Tags: API, Architecture, Infrastructure

Comments

  • See also:

    http://www.sitecore.net/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2011/08/NewsMover-Web-Controls-List-News-Articles-with-the-Sitecore-ASPNET-CMS.aspx

    - John West
    August 17, 2011 at 12:14 PM

*{0} must be filled in.
*{0} must be filled in.
*{0} must be filled in.