PPBe
/
parley_mainpage_ynh
Archived
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
A yunohost package contains the main page for https://parley.be
This repository has been archived on 2020-07-17. You can view files and clone it, but cannot push or open issues/pull-requests.
1 Commit
1 Branch
0 Tags
140 KiB
HTML 68.9%
Shell 25.2%
CSS 4.4%
Nginx 1.5%
 
 
 
 
Go to file
ilja d4e96a4c0b Initial commit 
The website is done in English.
There are some placeholder things for nl and fr as well, but the language header on the en page is commented out
There are no links in the README.md to the actual repo, only mentions to it

I wanted everything set up and done before changing those things
 		2020-02-28 08:15:58 +01:00
conf Initial commit 2020-02-28 08:15:58 +01:00
scripts Initial commit 2020-02-28 08:15:58 +01:00
sources Initial commit 2020-02-28 08:15:58 +01:00
README.md Initial commit 2020-02-28 08:15:58 +01:00
manifest.json Initial commit 2020-02-28 08:15:58 +01:00

README.md

Overview

Installation

yunohost app install <package-url>

Upgrading

yunohost app upgrade parley_mainpage_ynh -u <package-url>

For contributers

Translations

Adding a new translation to the site

  1. Copy sources/index_en.html and change the name so it has the correct two letter language code. The name should be of the form index_<langcode>.html
  2. Translate it
  3. Add a new block to the nginx config file conf/nginx.conf
  4. Add the new language to the language-menu of the other pages in the sources folder. E.g. for French -<a href="../fr/">fr</a>

Example of such block, change to the two-letter language-code:

location PATHTOCHANGE/<langcode> {
    alias ALIASTOCHANGE;
    index index_<langcode>.html;
}

Example of language-menu with languages nl and fr

    <div class='section language-menu'><a href="../nl/">nl</a>-<a href="../fr/">fr</a></div>

Improving existing translations

Adding things to the page

Make the changes to as many language pages as you can. The English page is considered the 'main' page, so please try to add it there as well.

Upstreaming

  • Bugs, feature requests and other issues can be logged on the issue tracker
  • Merge requests can be done to the stable branch directly

Publish a new version of the app

  • Updating will remove the folders and put the new version in place. As long as no big changes to the folder structure were done, you don't have to edit the upgrade script.
  • Technically we should edit the manifest file to bump the version, but having a verion system like this for a simple website seems overkill and updating will work regardless
  • stable is the default branch, so no need to merge to another branch