Promote Ultralingua case study [#945114]

This is a case study about a company called 'Ultralingua', who moved to Drupal:
http://drupal.org/node/933122

The company makes languages products, like dictionaries, spell and grammar checkers. They have private, corporate and government clients.

Before moving to Drupal, Ultralingu.com was built with static HTML files. This made it difficult for them to keep it up to date. Their move to a CMS was to allow company staff to update the site without having to re-build it.

Another major concern was the need to run it in several languages. Drupal's multilingual and translation-management system proved superior over the alternatives.

This is a classic example of a an established business who uses the website as a marketing tool. They say immediate benefits after migrating to Drupal and were happy to tell about it.

I've written a front-page case study before, so I have 'documentation' privileges. All attached images are already included in the post.

Comments

Comment #1

gdemet

he/him

English

Chicago, USA

commented 18 October 2010 at 18:11

Status:

Active

» Needs review

This is a good start, but I think this case study could be fleshed out a little more. As written, it seems like the basic CMS functionality and localization was helpful, but that using the block system for mega menus and introducing the workflow modules introduced complications that needed to be worked around. There's also a comment in the case study about potential improvements to the carousel functionality that could be made.

Case studies that get promoted to the home page of Drupal.org are typically "success stories" that talk about how Drupal was used to solve a client's business problems, not recently-launched sites for which the developers are still soliciting feedback for improvements. I'd like to hear other webmasters/site maintainers weigh in with their thoughts.

Comment #2

icanlocalize commented 19 October 2010 at 09:57

The business problem that Ultralingua had to solve here was that the older site couldn't keep up with the company's products.

Their products developed and the website was years behind. To them, it was a serious business issue. Drupal helped in the sense that now many employees, including folks that are not website experts can maintain contents.

Besides this, on a static site, maintaining hundreds of pages in several languages was an impossible task. As a result, they help off translation work until it all went to Drupal. Having multilingual content is pretty important for a company that sells language products.

I asked the designer to respond to the comment about the carousel. I don't think that they should do "design by committee" and make changes per comments in this post. It would be nice to have a courtesy response though.

What would you suggest to change in the post?

BTW - if there's an option to subscribe to comments, it's hiding pretty well. I can't find it.

Comment #3

gdemet

he/him

English

Chicago, USA

commented 7 November 2010 at 17:04

Thanks, this information definitely improves the case study. Given that no one else has posted in this thread in over two weeks, I'd like to hear the thoughts of some webmasters site maintainers before offering my +1

Comment #4

gdemet

he/him

English

Chicago, USA

commented 15 November 2010 at 15:31

As this issue has been open for nearly a month and no one else has commented in it, it doesn't seem like there's sufficient interest in promoting this to the home page. I'll leave it open another couple of days before marking as "wont' fix".

Comment #5

icanlocalize commented 16 November 2010 at 06:51

gdemet, thanks for the heads up and vote.

I think that d.o. folks were pretty busy with the new web design and this kind of non-critical thing must have gotten little attention.

Give me a few more days to raise interest and see if anyone can vote for this too.

Comment #6

robertdouglass commented 16 November 2010 at 15:23

I'd love to see this hit front page as translation issues are an important part of what makes Drupal special, but the English-centric Drupal.org posts under represent this aspect of Drupal. It's nice to see a case study about a multilingual site.

Full disclosure: I'm an advisor for ICanLocalize.

Comment #7

gdemet

he/him

English

Chicago, USA

commented 16 November 2010 at 17:04

That's a good endorsement for me, Robert, but just to be completely on the up-and-up, I'd like to see at least one other +1 from someone without connections to ICanLocalize as well.