From Fedora Project Wiki

The websites arch (build, dev and trans)

Our build system

Our websites are rebuilt hourly. This is done using the syncStatic script which is puppet managed. In other words, you need to be on the infra team to change it. A sample copy is uploaded there. This is where we decide against which branch we build each websites. There is also a specific syncStatic.stg script for the staging websites. Example of stg websites are and

For release time, please refer to our specific documentation there.


Many of our websites are using the 960 Grid System which is why you will see many divs on our HTML sources. You might want to see an explanation.


The fedora-web repository looks like the following (mostly all websites use the same tree as

  |   |-- data
  |   |-- Makefile
  |   |-- po
  |   -- static
  |-- build.d
  |   |--
  |   |--
  |   |--
  |   |--
  |   |-- pybabel.cfg
  |   -- translations.ini
  |-- httpd
  `-- tools

Each websites directory consists on a data folders holding HTML code, while all static code (JS, pictures, CSS…) are in static. Some websites use specific building files in the build dir if any. build.d contains the python building scripts and the Genshi template, as well as the language name localized for each luangages. The httpd folder contains standalone apache files to locally test our websites. tools is the place for manual script that we run times to time. In order to update the LINGUAS file, or to check the websites..


We use the Genshi framework for internationalization. Our current templates need to have special markup around the strings in order to mark them as translatable.

There are several way to use the markups.

  1. ${_('String')}
  2. ${Markup(_('String with > html code'))}
  3. ${Markup(_('String with a <a href="%s">link</a>') % '')}
  4. ${_('%(size)s, DVD ISO disc image for %(arch)s-bit PC') % {'size':'3.1 GB', 'arch':'32'}}
  5. ${Markup(_('If you think you\'ve found a bug, read <a href="%s">here</a> fist.') % (''+global_variables.release['prev_id']+'_bugs'))}

Fist you have the simplest example. Then the markup that could be used everywhere (it works with embedded html code, not as the first one). Then, you have an example using a variable. That is really useful in order to avoid having translators to translate again the string when changing the variable. The last example is a most complete one which shows you how to deal with multiple variables. The translator will be able to change the variable order using it's name.

To test that you haven't missed anything (for example you need to escape the simple quote from the string), try with make en test in order to build the website for the en language.

Once it's correct, you need to generate the new translation template file (POT) with make pot.


As described in the examples above, you will note there are a lot of variables instead of hard codes. These variables have been set to make it easier to update our webpages. When merging from one branch to the next, i.e. from beta to final release, all the content of our pages can be updated by editing simply one single file, where all the variables are defined.
This file actually is used in the sites of and in and is located in ~/build.d/


All POs are download twice a day. Any error should be reported to our tracking system.

Whenever the HTML content change, we need to update the POT as explained on the previous section. Then, we need to push this POT to the translation platform, This is done by the command make pushpot. But only the maintainers of the fedora-web release are able to push a new POT. Ask them if you need to do so. Please, open a new ticket.

Adding a new language is done through 4 steps:

  1. first, create it at by uploading a new translation on the website.
  2. Then, update the translations.ini file accordingly
  3. update the LINGUAS file (tools/ might be of help)
  4. update the local httpd/conf/language.conf file (by running make en test for example) and ask to make this change in the infra (puppet). That is probably needed as we have the same exact copy of this file there. File a ticket for that on our Trac.


Please read the Websites/Join and How to fix bugs pages.

Actual used branches for each (sub)domain

This overview should help you to understand which git-branch is used to build a single subdomain or domain.
Usually the subdomains are build with master-branch, while the main fedoraproject domain and the spins are build with the 'release-state' branch.

Domain Branch master f19-alpha master f19-alpha master master master master master master

The following table will show you which transifex resources are defined on each websites, and if the builder actually pull them. It should reflect the .tx/config file.

Website Transifex Resource Pulling Checkmark.png Checkmark.png Checkmark.png Checkmark.png Checkmark.png Checkmark.png Checkmark.png

Checkmark.png : Branched − the builder update the translations

Warning.png : Not branched − POs freezed, builder not pulling translations