Closed strump closed 5 months ago
Latest commit: |
82f2189
|
Status: | ✅ Deploy successful! |
Preview URL: | https://2877c827.organicmaps.pages.dev |
Branch Preview URL: | https://faq-plus-tts.organicmaps.pages.dev |
@Jean-BaptisteC thanks for feedback. I changed Android version question and fixed links to OSM.
Whant do you mean by "subtitle has been remove"? Do you have screenshot of road avoidance settings?
Subtitle IHM has been removed here https://github.com/organicmaps/organicmaps/pull/6251
I am not sure that the current structure would be straightforward to the user. For example, if I have an issue with routing in the Android app, it is "Android question" or "Routing question"?
My recommendation is to land the structure (at least two section with 1-2 sample questions in each) and discuss the content itself separately. Otherwise it will never end.
@rtsisyk with current structure we can put same question to different sections:
taxonomies:
faq: ["Android", "Routing"] # any number of sections you'd like
The question is going to be copied to all sections.
I agree that we should finish with structure and move to content.
Sharing the new design for the website which is in progress. The Support page will have a search of all the FAQ questions and each one can be tagged with category and OS (multiple categories and multiple OS). https://www.figma.com/file/oNEntnxkOIA0DrsTL1dRpD/Organic-Maps?type=design&node-id=0-1&mode=design&t=f9deMAqnVhny3buD-0
The progress of the site: https://preprod.organicmaps.pages.dev/
FAQ document with the latest updates. It still needs work, but includes questions/answers from all the sources available. https://docs.google.com/document/d/10i_7mv7w5LqO6QZLsqIT9pyIPNiXCVasyLkmsJ1LWsA/edit#heading=h.qrbphg2zgpo9
Sharing the new design for the website which is in progress.
Wow!! This brand new website looks quite promising!!!
What is your plan regarding the FAQs? Cause I'm currently dealing with the FAQs in the "zola" version of the website and I also see that you have a link to a Google Doc with a merge of different FAQs.
Please let me know that is the roadmap that you have regarding the FAQs, in order to optimize the work... Do you plan to move the FAQs in the Google Doc to the zola version? or will they go directly to the new website?
Note that google docs FAQ needs to be reviewed first.
The new website should work on Zola, so the FAQ section implementation from this PR should be helpful. CC borntojesus
@gpesquero The new website design will use the same underpinnings as the current website (Zola, Weblate), so your work with Zola aligns with the new website. Adding the new FAQ content will be independent of the website update, if the content is ready early, it can be added before the new website is launched.
The Google Doc still needs updating to clarify the question and answers. If you're interested in helping with that, I can give you access.
If you're interested in helping with that, I can give you access.
Sure, I can help updating these FAQs... I've already done some changes in the file with my Google account, which appear now as "suggestions"...
@gpesquero great, please request edit access in the Google Doc.
@gpesquero great, please request edit access in the Google Doc.
Sorry @oleg-pah, but I cannot find the way to request the edit access in Google Docs...
The only available modes are Suggesting or Viewing, but the Editing option is greyed...
... and there's is no "Request Edition" button anyware in the Google Docs interface or menu.
Can you please check if you can modify the Share options of this file to include my Google user?
@gpesquero I see that you requested edit access, you now have access.
What is preventing us from merging this PR? I need a structure to add more instructions.
Changed structure little bit. Now we have 3 levels:
/faq/
- list of subjects/faq/android
- list of questions for a subject/faq/bookmarks-02-remove/
- single question with answerSome questions has one line answer. But we show it on a separate page. E.g. /faq/android-05-webview/
. Is it ok?
Thanks! Separate pages are needed for SEO and sharing anyway, so I don't see a big issue here. And we always can generate combined index pages from separate answers.
The path of each answer should have only the question's text in it, like /faq/how-to-remove-a-bookmark
, ideally localized to different languages.
Added explicit slug
property to each FAQ page. Currently slug is a copy of title to get URLs:
/faq/how-to-measure-distances-with-organic-maps-is-there-a-ruler/
/faq/pochemu-marshruty-v-om-chestnye-i-otlichaiutsia-ot-drugikh-prilozhenii/
I had to change Zola config slugify.path
from "safe" to "on".
Thanks for the spirit to work on it!
android-01-version
to what-android-version-can-run-organic-maps
(and removing its index.md
slug) works just fine. Slug later can optionally be used for localized content for better SEO.extra: order: 10
variable is needed? Doesn't weight
work as expected?/faq/
index page? Current taxonomies /faq/android/
can stay as is, they are also convenient.I've already reviewed and updated the FAQ Google Docs document. I've left some comments in the doc with questions and doubts for some of the FAQ. Please review the document and provide feedback or answers to the questions raised...
My plan now is to move all the FAQs in this Google document into the FAQs in the faq_plus_tts
branch. I will mark with a special paragraph color all the FAQs being or already moved to the git branch.
Thanks for a lot of work! The first step should be to finish/finalize the FAQ structure. Only after that, we can start creating content files in the right way (with a proper path/name/header). @strump can you please help?
As you have already reviewed FAQ items, can you please help and incorporate the missing questions/answers from my user support notes? Many of them may already be incorporated.
They are not sorted, contain some duplicates, and may have non-questions items that should be rephrased. It also would be great to categorize FAQ items into different groups/tags, including ios/android.
Changed structure. Now we have 2 levels:
/faq/
(link) - list of subjects and question titles
/faq/bookmarks/how-to-add-intermediate-route-points/
- single question with answer
Refactoring of /contect/faq
folders structure.
@biodranik we can't get rid of extra.order: %d
property because Zola doesn't support "weight"
property for taxonomy pages. See comment in Zola github: https://github.com/getzola/zola/issues/246#issuecomment-408480599
Sorting in taxonomies is another can of worm that I hope to defer for as long as possible
please help and incorporate the missing questions/answers from my user support notes? Many of them may already be incorporated.
@biodranik @strump including the latest questions in this document.
https://docs.google.com/document/d/10i_7mv7w5LqO6QZLsqIT9pyIPNiXCVasyLkmsJ1LWsA/edit
Cool, looks great to me, many thanks @strump !
It would be great to make taxonomy/tags clickable in the /faq/ headers, and also list all tags at the top or at the bottom of each /faq/tag/ and /faq/tag/question/ pages.
@biodranik
On /faq/
page category names are links now (everything is blue).
Added second-level menu to FAQ category and FAQ question pages:
F.A.Q. • Android • Bookmarks • General • iOS • Map • Routing • TTS
But I don't know how to mark question category. E.g. on the page https://99f9f351.organicmaps.pages.dev/faq/android/what-android-version-can-run-organic-maps/ how to tell that the question relates to Android? What if page has two or three categories?
Hi there!!
I've already reviewed and completed the FAQs in the Google Docs file and I've also traced that all missing questions/answers from the 77 user support notes listed here are somehow included in the FAQs. This traceability can be found at the end of the Google Docs File.
I understand that the next step would be to start to include all the FAQs from the Google Docs file into the faq_plus_tts
branch, but first we also have to confirm which categories shall be used for the FAQs...
In the repository we currently have the following 7 "questions" categories:
And these are the 12 "categories" included in the Doc file:
Please confirm that these 12 categories are the ones to use...
@strump thanks! The structure is almost ideal now. I've tested it and suggest removing folders for categories and keeping all articles in the root faq folder. Then each article can easily have more than one (localized!) taxonomy category without a hard-coded path.
But I don't know how to mark question category.
I suggest introducing a templates/faq/page.hmtl
template and explicitly mentioning it in each md file as template: templates/faq/page.hmtl
for easier customization.
Then you can access any page's taxonomy by checking page.taxonomies
field.
@gpesquero before moving the content, let's polish this branch for the releasable state, by focusing on only a few articles first, translated into a few languages initially (as an example), so it can be merged. All other content can then be added later separately.
After a proposed fix, it would be very easy to edit/change the category of any article (or put it into several categories, or mark articles related only to iOS or to Android) at any time.
@biodranik when I wrote "But I don't know how to mark question category." I mean that I don't know how to visualize categories in top menu:
Make "Android" bold, different color, or with some icon?
@gpesquero before moving the content, let's polish this branch for the releasable state, by focusing on only a few articles first, translated into a few languages initially (as an example), so it can be merged. All other content can then be added later separately.
I've launched PR 204 with just a couple of FAQs as example for testing & validation. Please have a look at this PR, as it needs some fixing...
@strump it's not critical ATM, make it bold for example. We'll prettify it later, finishing with the structure is more important.
Let's add some ru translations to test if taxonomy works, to also help @gpesquero
@biodranik there's a problem with multilanguage and toxonomy in one project. See issue. Getting error faq\android-01-version\index.uk.md' has taxonomy 'faq' which is not defined in config.toml
.
I'll try workaround from that issue discussions.
@strump the same (or similar?) issue was mentioned by @borntojesus on the preprod branch.
The linked zola issue should be already resolved. It looks like taxonomies should be defined for each language separately (and maybe also duplicated in the root too).
What is the best way to reproduce the issue here?
@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: https://github.com/organicmaps/organicmaps.github.io/pull/185/commits/a997f3ce1e3e2e04d5cdf19f3b5301fabf788080
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.
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.
@biodranik I fixed FAQ templates little bit:
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?
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?
@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 %}
@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?
@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 😔
@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.
@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?
@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 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...
@biodranik should I close this PR after #212 is merged?
@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.
The FAQ structure based on this PR has already been merged. Only the content is needed now.
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 customextra.question
.Added ordering by
extra.order
field.weight
is not available for taxonomy terms.