Wiki - Main - CmsDocumentation

CMS documentation and rules

Publishing rules

There is a single person in charge of a single language. This person must ensure the following things:

Markup is valid (use Validator to make sure it is);
Markup is identical to what exists on the reference (ENglish) version;
The localiser has freedom to change the links to binaries and documentation in the local language, but not with the rest of the content.

Documentation for static part of the WWW content

There is an image containing text that will need to be translated, please send the translations of the following phrase to the ActiveMembers mailing list: "Make a donation".

Log on at http://backoffice.mozilla-europe.org/compose/auth.php
Read the documentation on the home page ;-)
Currently all files in your language section are the English reference files. Download the files (either by downloading them individually or through the "download a tarball of this directory" link). If you ever want to download all the English content as a tarball you can use this link.
Translate the files EXACTLY as is. Don't make changes to the markup, except for the lang and xml:lang atttributes and download links etc. Please note that there are 2 files with a different format, used for application localization (as opposed to HTML document localization). They are located in /languagecode/l10n/. main.lang is used for the headers and footers and members.lang is used for the membership application. Members.lang is slightly less urgent to translate
Upload the localized files using the CMS
Make sure there are no broken links, that the XHTML is valid and that the content is proofread by someone else with good language skills. You can view the results (with styling and header and footer as defined in main.lang) on the staging server (http://stage.mozilla-europe.org/). Links can be checked with http://backoffice.mozilla-europe.org/checklink/ by entering the URL to the page on the staging server (eg. http://stage.mozilla-europe.org/en/)
When everything's ready, ask for publication on the ActiveMembers list

Automatic product updates

This script's mission is to help us update the site more quickly when newer versions are released. It allows you to only have one central file to update instead of 3 when a new version of a product is available.

Please follow the following steps in order to use the script in your page:

Create or modify /your_lang/l10n/products.php

Reference: http://backoffice.mozilla-europe.org/repository/en/l10n/products.php

That file will contain all the infos the script need to work properly. It's pretty much self-explanatory.

The 'contrib' link must have a size of 0 and be an absolute link. If

you don't know the size of a build you are linking to, then use -1, not 0. (0 is a special case that causes the script to treat the link as absolute)

Call the script

Here are the functions you must use:

Print the latest version of $product available in your language.

?php $product[LANG]->printVersion(); ?>

Print the name + latest version of $product.

<?php $product['en']->printFullName(); ?>

For instance:

<title><?php $thunderbird['en']->printFullName(); ?></title>

Will print:

<title> Mozilla Thunderbird 0.8 </title>

Print the releases notes url.

<?php $product[LANG]->printReleaseNotesURL(); ?>

In the future I'll add some code to have a printReleaseNotesLink(); which will take care of the whole <a> tag and its attribute.

Print a complete download link.

<?php $product[LANG]->printDownloadLink('system'); ?>

Prints a complete download link, with hreflangs if needed, for 'system'; system can be win32, linux, macosx and contrib. If the size is more than 0, it converts it in megabytes and prints it after the link.

This is where it becomes a little trickier for you, because we have to take in account that your localized version isn't always the latest one available. When this happens, we need to display both the english version and the old localized version. On the homepage and products page, you must use the following code:

<?php printPlatformDownloadLink($product) ?>

On the products specific pages like /firefox/, /mozilla/, etc, you must use the following:

<?php if (isUpToDate($firefox[LANG], $firefox['en'])) { ?>
<ul id="nav">
<?php $firefox[LANG]->printDownloadLinks('li'); ?>
</ul>
<?php } else { ?>
<h3 class="prod"><?php $firefox['fr']->printVersion(true); ?></h3>
<ul id="nav">
<?php $firefox['fr']->printDownloadLinks('li'); ?>
</ul>
<h3 class="prod"><?php $firefox[LANG]->printVersion(true); ?></h3>
<ul>
<?php $firefox[LANG]->printDownloadLinks('li'); ?>
</ul>
<?php } ?>

If for some reason there are no localized build for a system, then call the 'en' version for that system. I'm working on a better way of handling this particular issue.

Add translations in main.lang

The script uses 2 strings you need to translate: 'Other operating systems' for all 'contrib' links, and 'MB' for megabytes.

Please insert the following at the end of /your_lang/l10n/main.lang in the cms:

;Other operating systems Your translation here

;MB Your translation here

News

Introduction

The news system is now using dotclear?. Not all languages are using it currently, because we need to wait the import of the old news to be finished (otherwise we wouldn't be able to publish index.html and press.html when needed, because that would publish a version that doesn't have all the news items). The languages using it now are fr, en and es.

What you need to know about the pages on the CMS

press/ should be gone, we replaced it with press.html
some php code was added in index.html and press.html. Please don't touch that code ! press.html contains lots of code, but hopefully you shouldn't need to touch it.
everything is automatic, Dotclear fetches the news for you. No more manual editing when addind a news item.

How to add a news item?

How to add make a press release?

Editing

Wiki syntax

Wiki syntax may be used within Dotclear only (e.g. not in static pages).