Switch branches/tags
Nothing to show
Clone or download
Latest commit 96c414f Dec 12, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
_includes new TUB papers Nov 19, 2018
_layouts fixed typo (consistenly wrong at least) Oct 17, 2018
_notes link in some distribution documentation on the help page Jan 31, 2018
_posts aanouncing 2018/12 release Dec 10, 2018
_site regen Dec 12, 2018
about draft2 Oct 16, 2018
bugs change suggested by Bruno Dec 15, 2017
css split out years 2010-12 as well; separate conferences by a rules Jun 28, 2018
fa initial commit, website contents Jan 15, 2016
fonts menu styles and responsiveness Feb 24, 2016
help aanouncing 2018/12 release Dec 10, 2018
img news post Oct 17, 2018
js rewrite (kinda) of cookie consent. Got rid of external requests, Sep 18, 2016
latex3 dropped gmane ... long dead Oct 28, 2018
lppl news updated, footer links, last modified date added to footer, minor… Jan 20, 2016
news typo Dec 12, 2018
publications new TUB papers Nov 19, 2018
.gitignore added CI article as submitted Jan 22, 2018
Gemfile added colorator to Gemfile, regenerated Gemfile.lock and generated Sep 18, 2016
Gemfile.lock added TUB paper Sep 14, 2017 Update Jan 22, 2018
_config.yml changed baseurl in _config.yml, site update Jun 28, 2016 news updated, footer links, last modified date added to footer, minor… Jan 20, 2016
favicon.ico added favicon.ico Feb 17, 2016
feed.xml all the other changes Feb 10, 2016 add info on TL status in different Linux distributions Aug 25, 2018
googleb76b73e63d2a62c5.html google site verification (frank) Sep 2, 2016
googlecbd1f799c29b66a7.html initial commit, website contents Jan 15, 2016
index.html show 3 recent news entries not 2 Sep 23, 2016
lppl.txt initial commit, website contents Jan 15, 2016 some further explanation in the privacy statement May 24, 2018
robots.txt deleted feed Aug 31, 2016

Changes to the master branch can be viewed at, which is the staging environment. If everything looks fine, you can merge master with live to have the server running pick up the changes.


The staging - master branch

The website - live branch


If you want to develop locally first, this is the way to contribute:

  • Fork this repository (and make sure you are in sync with it if you forked a while ago).
  • Create a new branch for your changes: git checkout -b branch-name.
  • Make your changes.
  • Commit locally and push that to your repo.
  • Send in a pull request based on the above.

You can also edit/commit directly to the gh-pages branch on github:

  • Go to the file/directory you want to edit.
  • Make your changes.
  • Add a message describing your edit.
  • Commit directly to the gh-pages branch / Create a new branch for this commit and start a pull request.


In order to contribute to the website’s codebase, you’ll need to know a bit about Git, Jekyll, CSS or Sass, Markdown, and some Command Line-fu. You'll also need to know how to install Ruby Gems and of course have Ruby installed on your machine.

Local Development

Gem Installation

Use the bundle command to install the necessary gems for the LaTeX Project. If you don't have bundler installed you'll need to run gem install bundler before using bundle.

$ bundle install


Trigger the local server by executing the jekyll serve task.

$ jekyll serve

Your local copy will now be accessible at http://localhost:4000. Then use CTRL + C to stop the server.



Webdesign License

The webdesign by Jonas Jacek is licensed under a Creative Commons Attribution 4.0 International License. Based on a work at

This is a Free Culture License!

However, the license requires you to give appropriate credit to Jonas, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests Jonas or the LaTeX Project endorses you or your use.

Please credit Jonas with a link to his website ( and state the license somewhere on your page. Everything else brings bad karma.

Reporting Website Bugs

If you think you've found a bug on our website you can report it to the website team at If you do submit a report, thanks for taking the time!