Add F.A.Q. section

[strump]

Fixes #6

I picked PR #171 "[WIP] Added text to speech instructions" and added F.A.Q. questions from @biodranik coffers. Implemented using Zola taxonomies.

Almost all screenshots are made on Android.

Blank spaces are present.

What to do with *.po files? Should I add texts from new pages to PO file?

Update 2023-10-09

Create subfolder for each FAQ question.

Using title propety instead of custom extra.question.

Added ordering by extra.order field. weight is not available for taxonomy terms.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	82f2189
Status:	✅  Deploy successful!
Preview URL:	https://2877c827.organicmaps.pages.dev
Branch Preview URL:	https://faq-plus-tts.organicmaps.pages.dev

View logs

[biodranik]

@strump let's polish this branch and prepare it to merge. If there is not enough time to read all texts, let's select one simple FAQ page and translate it to all languages, according to this commit: a997f3c

Existing content can stay on this or another branch, and then we can continue improving it after rebasing to the master branch with the ready structure.

[rtsisyk]

Please push a branch with 1-2 FAQ articles for the beginning, in English. I have been waiting for this new FAQ section for months.

[strump]

@biodranik I fixed FAQ templates little bit:

• Added translation for FAQ breadcrumbs
• Added RU translation for a single Android related question

Problems I see so far: you can't change language from https://faq-plus-tts.organicmaps.pages.dev/faq/ and https://faq-plus-tts.organicmaps.pages.dev/faq/android/ pages. Language selector (top right link) doesn't work with taxonomies, because those taxonomies have no list of supported languages. Only FAQ questions have language selector (if translations are available).

I'm little bit lost with next steps. What structural changes do we need? What text related changes do we need?

[gpesquero]

I've fixed PR 204 so the FAQs also work now for Spanish language.

One issue that I've noticed in the resulting FAQ list in Spanish...

...is that the "Aplicación preguntas" text is incorrect, as it comes from the direct composition of the translation of the taxonomy name "App" and the string "questions". In Spanish (and in many other languages), the word order shall be the opposite ("Preguntas (de) Aplicación").

This taxonomy+question word order comes from the code <h3><a href="{{term.permalink}}">{{term.name}} {{ trans(key='faq-questions', lang=lang) }}</a></h3> in the file templates/faq/list.html. Could it be possible to have different versions of this file for every/some languages to arrange correctly the word order?

[biodranik]

@gpesquero yes, you can add something like {% if lang == "es" %}{{ trans(key='faq-questions', lang=lang)}} de {{term.name}}{% else %}{{term.name}} {{ trans(key='faq-questions', lang=lang) }}{% endif %}

[biodranik]

@strump did you try to set lang explicitly in taxonomy? Maybe dumping all available variables help to get list of translations?

If languages issue is fixed, then we can cleanup the code and merge it to the master. Do you see any other issues?

[strump]

@biodranik I can get the current language for a taxonomy, but I couldn't find all available languages for a taxonomy.

For example, "Android" taxonomy is currently available in two languages, while "Map" taxonomy has only "en" translation. But I don't know how to get a list of all available translations to enable language switcher.

Taxonomy+Translation = pain 😔

[biodranik]

@strump you can access all currently configured taxonomies and their translations from global var languages["ru"].taxonomies[], which may be similar to the already existing code that scans page translations.

But I don't think it's a blocker, let's focus on other issues and polishing the final version for merging, this fix can be done later.

[strump]

@gpesquero @biodranik maybe we should replace

faq-questions = "questions"

with somethink like

[languages.en]
faq-questions = "%1 questions"

[languages.es]
faq-questions = "Preguntas de %1"

What do you think?

[strump]

@gpesquero Let's try another option. I removed work "question"/"pregunta" completely. Let's use just taxonomy names as titles: "Android", "Map", "Routing".

And you can translate taxonomy terms: "Mapa" instead of "Map", "Ruta" instead or "Routing". Please try and tell how it looks now?

[gpesquero]

@gpesquero Let's try another option. I removed work "question"/"pregunta" completely. Let's use just taxonomy names as titles: "Android", "Map", "Routing".

This approach is simpler and will give us less "headaches", so it looks good to me...

PR 204 updated accordingly...

[strump]

@biodranik should I close this PR after #212 is merged?

[biodranik]

@strump I think yes, you did a lot of work, thank you very, very much!

It may make sense to leave content articles though for future updates/modifications.

[biodranik]

The FAQ structure based on this PR has already been merged. Only the content is needed now.