sale-bubble sign-up-large

30% Savings on all Shared Hosting packages and billing cycles
Offer is valid for any shared hosting package & billing cycle including 1, 2 and 3 year accounts. Offer is limited to 1 per customer, is a one-time discount and for new accounts only. To take advantage of the offer use PROMO CODE: SAVE30 when placing your order.

JVIS – A global website for an auto-parts maker

Blog - Drupal


{joomad pos=left rssid=100} {joomad pos=top rssid=100}{joomad pos=right rssid=100}

JVISJVIS USA LLC is an international supplier for automotive components and tooling with facilities in 6 countries and customers all over the world. Their website helps them introduce their products to auto makers.

Going multilingual

When JVIS commissioned their website, they requested just a few static pages. It was built as a simple static HTML site (no CMS) and in English. Very soon after launching their new site JVIS decided to localize to Japanese, Chinese, Korean, Russian and Spanish. These are the languages spoken by their larger clients.

At that point Jason Marshall contacted us about translating JVIS' website. It was already built (as a collection of 23 HTML files), ready to be translated. Our translation service would have produced another 92 static HTML files which JVIS would have uploaded to their server. It was clear that JVIS was going to be adding new content on a regular basis and maintaining it all in several languages without using a content management system would have been a very unwelcome task.

The likely possibility of turning a client from being happy to frustrated, due to this manual content management, concerned us very much.

We suggested to Jason Marshall, the web designer who built JVIS website, to first migrate it all to a CMS and only then begin the translation process. The first choice was Drupal, given its powerful multilingual capabilities. Maintaining a multilingual Drupal site would be much simpler, not just for us, but mostly for the client. From the client's point of view, only English texts would need to be managed. Drupal would automatically handle everything else.

read more

{joomad pos=bottom rssid=100}

busy



Disclosure: Content posted to this site is in no way an endorsement for a product or service and may result in compensation from the vendor. Some content contained in this site is syndicated content.