anchor.diff:  Here is the list and description of all technologies used to build and run the website.
   
   === Design
  -* _http://foundation.zurb.com/[Foundation]_: loud shout out to the folks behind this framework that made rapid creation of nice looking websites possible.
  +* _{foundation-uri}[Foundation]_: loud shout out to the folks behind this framework that made rapid creation of nice looking websites possible.
   
   === Layouts, content and data
   This is the core content of the website. Layouts, forms, prose, all written using this troika.
   
  -* _http://slim-lang.org[Slim]_: this is a templating language used instead of pure HTML. It allows to write layouts and custom pages faster (no more closing tags, really!) as well as embed select code for baking the website.
  -* _http://asciidoctor.org[AsciiDoc]_: the syntax used for all content pages. This markup is much more featureful than _Markdown_, _reStructuredText_ or _MediaWiki_.
  -* _http://yaml.org/[YAML]_: the format of front matter and data lists. You can see it both in .yml files and at the top of some others delimited with `---`.
  +* _{slim-uri}[Slim]_: this is a templating language used instead of pure HTML. It allows to write layouts and custom pages faster (no more closing tags, really!) as well as embed select code for baking the website.
  +* _{asciidoctor-uri}[AsciiDoc]_: the syntax used for all content pages. This markup is much more featureful than _Markdown_, _reStructuredText_ or _MediaWiki_.
  +* _{yaml-uri}[YAML]_: the format of front matter and data lists. You can see it both in .yml files and at the top of some others delimited with `---`.
   
   === Coding
   The cogs of the website.
   
  -* _https://ruby-lang.org[Ruby]_: compile-time logic for site generator.
  +* _{ruby-uri}[Ruby]_: compile-time logic for site generator.
   * _JavaScript_: client-side runtime code. Examples: smooth scrolling, locale-based redirection.
   
   === Translation
  
positive.code: = Rigs of Rods website
  
  This is the source code for Rigs of Rods website. It is 100% static, fast and secure but uses a myriad of web tech to compile and run as intended.
  
  
negative.code: ==== Content pages
  This is pure prose and having wall of texts in a single data file is unfeasible. Hence we take a different approach here.
  
  * _{gettext-uri}[gettext]_: internationalization system used in Rigs of Rods and thousands of other software projects. Translations are stored as .po files which contain pairs of source string and translation along with some meta info about the author, group, language etc.
  * _{po4a-uri}[po4a]_ and _{po4a-bulk-uri}[po4a-bulk]_: gettext is a tool originally designed for software and software only. However, po4a authors beg to differ. This handy tool allows creation of gettext templates out of different document formats (AsciiDoc, man, POD and others) and generation of translated versions. _po4a-bulk_ is a wrapper around po4a written by https://github.com/skybon[yours truly] for handling large sets of files with po4a.
  
  For every content file in /content directory *po4a-bulk* calls *po4a* which in turn calls *gettext*. Resulting PO files can be edited by hand (say hello to good ol' notepad) or via dedicated tool (http://projects.gnome.org/gtranslator/[GTranslator], https://poedit.net[POedit], https://userbase.kde.org/Lokalize[Lokalize] and others).
  
  