Proof of concept of combined localized items in backend content item List

Topics: Announcements, Core, Writing modules
Nov 22, 2012 at 3:42 PM
Edited Nov 22, 2012 at 3:54 PM

When you have a website with a few different languages the list of content items becomes messy.

That's why I started a module which tries to solve those problems by combining content items. I would like to get some feedback and hear from you guys if it's a good idea or you have something better in mind. 

I've setup a new project on codeplex on but it's far from finished so currently it's only used for version control for myself :)

Here's a screenshot to see the current process:

Nov 22, 2012 at 3:48 PM

Could you display just the first piece of content with the title localised to the current culture.

Then have a space delimited list of cultures you click to view? with an action like +Create New Culture?

Nov 22, 2012 at 4:23 PM
Edited Nov 22, 2012 at 7:46 PM

Added the Create new Translation button, See new screenshot:

The list of translations is kind of a accordion but you can expand and collapse multiple.

Nov 26, 2012 at 7:43 AM

What do you guys think of the idea and the implemented usability of the latest screenshot?

Nov 26, 2012 at 8:24 AM

Sounds like a great idea, but I'm not sure we need a different tab for that.

Also, I'd like to see how that varies depending on the current culture.

Being able to make the default culture of an item different from the default culture of the site would help a few people as well. That's an idea that would easily be included in this view.

Nov 26, 2012 at 9:18 AM

Yes I agee this doesn't need a different tab but I didn't want to replace the original in the proof of concept so you can compare the two. Well currently it uses the original content item as a parent item but it's a good idea to vary this by current culture.

On thing I don't like is that I couldn't use the default Query method of the contentmanager and neither HQL, because of the "more complicated" where and join statement in the query. To accomplish this I've used a plain Session sql query. Maybe we can find a better solution?

@bertrandleroy: Do you see this feature as something we could build into the core or as a separate module?

Nov 26, 2012 at 9:36 PM

I'd prefer to see this as an improvement of the official Localization module.