quick post on finalized UX report, yay xenia vadym and all who helped! (#169)
* quick post on finalized UX report, yay xenia vadym and all who helped! * shift file * fix png filename
|1 month ago|
|.github||1 year ago|
|_includes||6 months ago|
|_layouts||5 months ago|
|_posts||1 month ago|
|assets||1 month ago|
|ca||1 month ago|
|de||1 month ago|
|en||1 month ago|
|es||1 month ago|
|fr||1 month ago|
|it||1 month ago|
|nb||1 month ago|
|pl||1 month ago|
|pt||1 month ago|
|ru||1 month ago|
|sq||1 month ago|
|tools||5 months ago|
|uk||1 month ago|
|.gitattributes||2 years ago|
|.gitignore||5 months ago|
|35c3.html||8 months ago|
|404.html||2 years ago|
|Gemfile||2 years ago|
|Gemfile.lock||2 years ago|
|LICENSE||2 years ago|
|README.md||7 months ago|
|_config.yml||8 months ago|
|_redirects||7 months ago|
|favicon.ico||2 years ago|
|feed.xml||2 years ago|
|google2faa16b6e4ce3d8b.html||2 years ago|
|index.html||6 months ago|
This repository contains the default website of Delta Chat - feel free to edit any file as you like and send a pull request.
In the various source text files that are used for generating the static https://delta.chat website we use Semantic linefeeds to keep "diffs" for changes small. The gist of it is that you put each "phrase" part of a sentence into a single line.
In the directory
_posts create new file in the form
eg. by copying an existing file
Write your blog post to the file and do not forget
to add or modify the
author: line atop
You can create your fork on Github and Github pages;
the forked website will then be available at
Alternatively, install Jekyll
on your local machive
jekyll serve --destination <path-to-build-dir>
in the source directory.
/en - Contains the source language files in Markdown. Can be edited directly.
fr ... - Contain the translated files;
translation is done through .po files that are translated using Transifex, see above.
You must not edit translated files directly here
but you can add additional files that are unique to the language.
/_layouts - This directory contains a default layout template
for each language (the layout is referenced in Markdown using layout: name)
/assets - Page specific images and files;
in general, we use one subdirectory per page or section here.
/assets/css - CSS and layout specific images and files here.
You can edit and improve the existing translations
To update existing translations from the Transifex server,
see the scripts and the documentation in the
To add a new language, the followinging steps are required once:
create a new layout in
and make sure that this layout is referenced in the
corresponding Transifex entries as
add the language to
./t-dance.sh pull from the
check the language selection in
To add a new page:
create the source as
tools/.tx/config as needed
and create dir
cd tools; ./t-dance push
whereever possible, use Markdown instead of HTML, esp. in the files that should be translated
the layout should be as simple as possible and should always work on small mobile screens as well as on desktops
when layouting, do not force a special structure. Header, Content, Footer - done.
no complex navigation - Simply link subpages from the main pages
no one-page-layout - we also have sites with long text, and we do not want to have separate layouts
we do not want a complex navigation, some toplinks, a footer, done.
Remember: Form follows function, KISS. The site should be dead-simple.
Finally: Have fun :-)
Licensed under the GPLv3, see LICENSE file for details.
Copyright © 2017-2019 Delta Chat contributors