Add translations to the main site (+markdown transition) [DON'T MERGE] #621
No reviewers
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#621
Loading…
Reference in New Issue
No description provided.
Delete Branch "i18n"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We will slowly transition from HTML to Markdown, wherever practical. This will result in much more readable and newbie-friendly files.
The first commit in this branch shows how we will implement localization. The main site will be multilingual -- this doesn't mean that the forks can't have their own repos and domains. It will be much easier for them to keep up, due to the utilization of
JSONYAML language files.instead of JSON to avoid painful escaping of"
.---
key: value
index.html
, you use localized strings like this:index.html
would override the variables.index.html
is now in_includes
languages/
includeindex.html
and set the language for it._includes/langs/
look like this: This allows for using {{ title }} instead of {{ lang.title | default: en.title }} in the md files (or the index.html file, depending on how we decide. See below.).I am not sure about this, but likely we'll do it this way:
_include/content
<<filename>>
being the name of the file without the extensionindex.html will be full of content includes, but the advantage is that we'll have far less conflicts.
I haven't yet decided what all will be converted into markdown.
It would be cool if we could convert
# headings
into headings with an anchor link and a FA link icon.
I guess moving the VPN comparison table to a separate file will be great, as index.html will be far less bloated.
The navigation thing on the right shows how big the VPN comparison table is.
Things like
Can be converted into markdown easily and it will be a great thing.
I guess this could be converted nicely into markdown, though I'm not sure about
img-fluid float-right
.It's important to keep in mind that we can freely use HTML in MD. At least on GitHub. Seems to be that way for most MD compilers. So this will likely be true in Jekyll/Liquid as well.
Will we move these sections to separate files too?
@Vincevrp
38954bc363
Activist:
The created file in
content/
starts with@Shifterovich what do you think of adding icons to the header template as they are now present at https://privacytools.ru? Also, I've made some re-ordering of the sections (and actually added a couple, which are only relevant to RU - so probably we should consider "floating sections"), so if you believe it makes sense, I can help with both things on the main template.
Good idea, that might for now solve the issue with the messy navbar. It will be easier to navigate in it.
BTW, after discussing this with @Vincevrp we came across two things:
So we will simply split index.html into markdown files by sections.
Closing in favour of #730.