- Removed the 'untranslated.html' snippet (_includes/untranslated.html). Since now we are using 'disclaimer.html' everywhere
- Replaced the old snippet with the new disclaimer (introduced with #966) in all Moneropedia entries
- Add snippet where it was missing
- Updated instructions in the README
- Fixed some interactive elements which weren't focusable (using 'tabindex')
- Label interactive elements which weren't labelled
- Slightly increase contrast of the grey text in the top navigation bars to reach level AA in the WCAG rating system and increase visibility of the text
- Use 'jekyll-feed' plugin to manage RSS feed and remove existing feed.xml file
- Add feed image in main blog tab ('All posts')
The 'jekyll-feed' plugin makes possible for aggregators to automatically detect the existence of a feed (feed_meta tag in header)
and creates a 'feed.atom' file containing the last 20 blog posts and locates it in the root directory. The structure is compatible
with our current system, including the possibility to show a picture if it's included in the post (#1002).
The old logo showing on social medias is too large and end up being trimmed. Replaced it with the simple Monero Logo.
If an image is specified using 'image:' in the front matter of a blog post, jekyll will show that image instead. This also allow us to easily
make specific meta-images for each blog posts. I will add the possibility to add the image in the body of the post in a
subsequent PR.
Removed completely the 'The Monero Project' page and related entries in _i18n/en.yml. Replaced entry in header with 'Translate', which links to Weblate (translate.getmonero.org)
This new approach doesn't require version numbers and make easier for contributors to understand the status
of the document. There are only 3 states:
- Outdated: The page is outdated and might not work as expected
- Untranslated: The page needs to be translated
- Translation outdated: The page is translated, but the original (English) document has been updated
To mark a guide as outdated, we change the boolean of the front matter entry 'outdated' in /resources/user-guides/GUIDE.
If 'False', the guide is updated. If 'True' all versions of the guide (English included) will show a warning at the bottom
of the page.
The other 2 states are related to the status of the translated pages and we control them from the language-specific
user guides: /_i18n/LANG/resources/user-guides/GUIDE. At the top of the page a snippet will include 2 parameters:
- translated: "yes" if the page is translated, "no" if it's not.
- translationOutdated: "yes" if the translation is outdated, "no" if it's not
This new system aims to be simpler than the precedent, avoiding to compare versioning numbers and using a higher level
system instead (yes, no, True, False). I also removed the middle way status 'only minor changes', because if there are
only minor changes that don't affect the usability of the guide, we don't need to point it out.
The old system was complex and people didn't use it. These changes will hopefully make things easier for translators and
other contributors.
Removed the '404' folder with its content and created a new '404.html' file in the root directory, added some specific css and slighlty edited the 'error' layout.
The list of languages doesn't need to be translated, so there is no reason to keep it in the language files. Moved to its own
file (/_data/languages.yml). Now the language dropdown parses the languages from there.
This change is also needed for the migration to Weblate (which would ask translators to translate the language names).
+ All guides are version
+ Major diff on Polish daemon RPC guide
+ Minor diff on Polish daemon RPC guide
+ yml completed for en, fr, pl, it, es
+ Instructions updated on readme.md:
- For Guide création: adding the mainversion to the /ressources/user-guides, the guide version and the translation snippet to the localized files
- For Guides update: how, where and why handling the version number.
- Updated README to accomodate for changes
- Updated footer and roadmap for multi-lingual readiness
- Updated yml files for an 'untranslated' string
- Added an 'untranslated' snippet to all untranslated files
- Added a 'template' language for new languages to be made easily
- Added link to Monerujo site to Downloads page
- CSS updates
- Adjusted values in en and es yml files
- Minor tweaks in a few pages
- Changed head rules to pull correct page titles
- Changed footer and header to loop correctly without a case statement and pull translated strings
- Adjusted FFS layouts
- Added support for multilingual navigation
- Put Spanish copy in some pages in get-started for testing purposes
= Added multilingual support for the home page
