csn-uk
CSN-UK | Charlie
Recently reading an article about language files and involving the recommendation for a method of best providing multilingual support across a site and justifying a method over another it sparked the writing of a tutorial however as part of that a justification was written.
I’m hoping it may open the eyes to a number of developers and hopefully appeal to your businessman/woman side, it ties closely to the topic of automation to streamline your business process and reduce costs, though potential a more practical example.
Consider having multiple sites (one for each language) for the purpose of this example mysite.com has 5 language options and 15 accessible pages. This then means if the webmaster where to change the content on 6 pages, he would need to edit 30 pages (6 pages x 5 languages) which at 1 minuet (find/replace) and the addition of uploading 30 pages possibly 1 or 2 minutes the time to edit the site would be 32 minutes.
Now this sounds like little time, however further consider the rate that a webhosting site or similar news or blog or E-commerce sites change.
Now consider the cost of your web development team, per member per hour, in the UK a junior web developer would be around £10/hour which is £2190/year per person to spend 32 minutes per day.
With that said now consider the use of an alternative method that is now very common, as before our site has 5 languages and 15 accessible pages however now we are utilizing language_gb.php, language_us.php ... and so on for our 5 languages all holding the changes that we make to the content to the different languages.
To further this we use a PHP function (later discussed) to check the user’s browser, and location we then load the browsers specific style sheet and language file by default based on the information (use of a simple IF Statement and PHP function).
This I hope as explained is a very simple example of a very common and miss looked problem when companies and start-ups select the wrong technologies or get into a bad practice. It is one of the main aims of software engineers (myself for example) to highlight these bad practices when asked to produce new systems for example and even we get tarred by the same brush now and again
I’m hoping it may open the eyes to a number of developers and hopefully appeal to your businessman/woman side, it ties closely to the topic of automation to streamline your business process and reduce costs, though potential a more practical example.
Consider having multiple sites (one for each language) for the purpose of this example mysite.com has 5 language options and 15 accessible pages. This then means if the webmaster where to change the content on 6 pages, he would need to edit 30 pages (6 pages x 5 languages) which at 1 minuet (find/replace) and the addition of uploading 30 pages possibly 1 or 2 minutes the time to edit the site would be 32 minutes.
Now this sounds like little time, however further consider the rate that a webhosting site or similar news or blog or E-commerce sites change.
Example 1
Possibly once every day? 32 (min) x 365 (days) = 13140 minutes or 219 hours or 9 days
Now consider the cost of your web development team, per member per hour, in the UK a junior web developer would be around £10/hour which is £2190/year per person to spend 32 minutes per day.
With that said now consider the use of an alternative method that is now very common, as before our site has 5 languages and 15 accessible pages however now we are utilizing language_gb.php, language_us.php ... and so on for our 5 languages all holding the changes that we make to the content to the different languages.
To further this we use a PHP function (later discussed) to check the user’s browser, and location we then load the browsers specific style sheet and language file by default based on the information (use of a simple IF Statement and PHP function).
Example 1 - Solution?
Now instead of 30 files we have 5 to edit, which as before 1 minuet per page totalling 5 minutes with the addition of 2 minutes to upload the changes meaning 7 minutes and again as before the same calculation
7 (min) x 365 (days) = 2555 minutes or 106 hours or 4 days
This then means £1060 identically as before is spent for the same change, meaning you are saving just over half, could you afford to lose £1130/year for a single daily site change?
Example 2
Now just to see if this sets in, imagine you where the financial director for apples website on your current webhosting budget, with 44 languages and for the purpose of this example you have 250 pages (sound fair?) and the same upload time 2 minuets
Now we change 2 pages daily (news/announcements)
90x365 = 32850 minutes or 1369 hours or 57 days at £13,690
Vs
46x365 = 16790 minutes or 700 hours or 29 days at £7000
This I hope as explained is a very simple example of a very common and miss looked problem when companies and start-ups select the wrong technologies or get into a bad practice. It is one of the main aims of software engineers (myself for example) to highlight these bad practices when asked to produce new systems for example and even we get tarred by the same brush now and again