posting a link to getmonero on social medias results, except few
exceptions, in showing a standard description for all pages.
This adds dedicated meta descriptions for every page. It will
improve getmonero's seo score and links on social medias will
look nicer and will be more descriptive
- Add link to the footer
- Add _includes/onion.html (the address will be pulled from here anywere on the website)
- Add /onion.txt which is signed by binaryFate and contains the onion addresses
- Add onion-location header as a meta tag in _includes/head.html
Co-authored-by: binaryFate <binaryfate@getmonero.org>
I moved some stuff around, added nad removed some entries, added a link to the Sitemap, removed the IRC Section and replaced with a more generic 'Reach Out' section.
This is the last part of the refactor, which allow us to remove the _data/lang folder with all its content and make the footer use the 18n plugin. Now only the user guides and the Moneropedia are outside the localization system.
- Removed the _data/lang folder and all its content
- Since most of the entries are duplicates of the 'titles' in LANG.yml, we use those. For the two missing ones we add a 'footer' section
- Edited the README
- 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.
