WIP: Import FAQ section from the main repo #115

rtsisyk · 2023-02-11T13:33:02Z

rtsisyk commented

2023-02-11 13:33:02 +00:00

English text is imported from 1 as-is without any edits.
Improvement of content is out of the scope of this change.
Translations will be enabled by subsequent changes.

Please don't spend energy discussing the content itself. The goal of the commit is to add the FAQ section for future improvements and expansion.

Signed-off-by: Roman Tsisyk roman@tsisyk.com

- English text is imported from [1] as-is without any edits. - Improvement of content is out of the scope of this change. - Translations will be enabled by subsequent changes. Please don't spend energy discussing the content itself. The goal of the commit is to add the FAQ section for future improvements and expansion. [1]: https://github.com/organicmaps/organicmaps/blob/22f797a9c3f398f400d9774a47f253b4d15188d0/data/faq.html Signed-off-by: Roman Tsisyk <roman@tsisyk.com>

cloudflare-workers-and-pages[bot] commented

2023-02-11 13:33:19 +00:00

(Migrated from github.com)

Deploying with Cloudflare Pages

Latest commit:	`89877b1`
Status:	✅ Deploy successful!
Preview URL:	https://55b61251.organicmaps.pages.dev
Branch Preview URL:	https://rt-faq.organicmaps.pages.dev

View logs

## Deploying with  <a href="https://pages.dev"><img alt="Cloudflare Pages" src="https://user-images.githubusercontent.com/23264/106598434-9e719e00-654f-11eb-9e59-6167043cfa01.png" width="16"></a>  Cloudflare Pages <table><tr><td><strong>Latest commit:</strong> </td><td> <code>89877b1</code> </td></tr> <tr><td><strong>Status:</strong></td><td> ✅  Deploy successful!</td></tr> <tr><td><strong>Preview URL:</strong></td><td> <a href='https://55b61251.organicmaps.pages.dev'>https://55b61251.organicmaps.pages.dev</a> </td></tr> <tr><td><strong>Branch Preview URL:</strong></td><td> <a href='https://rt-faq.organicmaps.pages.dev'>https://rt-faq.organicmaps.pages.dev</a> </td></tr> </table> [View logs](https://dash.cloudflare.com/?to=/:account/pages/view/organicmaps/55b61251-bd0a-49b6-b58b-87f08b4972be)

biodranik (Migrated from github.com) reviewed 2023-02-11 21:39:42 +00:00

biodranik (Migrated from github.com) left a comment

It's hard to sync and add new sections in one large file.

FAQ is easier to support if it will be split to subsections, each with its own page for each entry. It simplifies the addition/translation of a new item and allows to add more images to any item if necessary (think about TTS or small animations about a feature). Also, keeping separate subpages with images will help to avoid overbloating of the index page that can have only titles of the subpages for example.

I already have a list of 50+ items for FAQ.

A structure similar to News can be used.

It's hard to sync and add new sections in one large file. FAQ is easier to support if it will be split to subsections, each with its own page for each entry. It simplifies the addition/translation of a new item and allows to add more images to any item if necessary (think about TTS or small animations about a feature). Also, keeping separate subpages with images will help to avoid overbloating of the index page that can have only titles of the subpages for example. I already have a list of 50+ items for FAQ. A structure similar to News can be used.

content/faq/index.md

					
				@ -0,0 +84,4 @@

				Alternatively, to plan a route, you can press "Route" icon in the bottom menu panel. You can choose different starting point (Route from button) to preview a route, but navigation is only available from your current location.

				You can add up to 3 intermediate points to a route. To add an intermediate point: create a route between start and destination → then tap a point on the map and tap "Add stop".

biodranik (Migrated from github.com) commented

2023-02-11 21:31:32 +00:00

100

content/faq/index.md

					
				@ -0,0 +100,4 @@

				- If you are an Android user and the option is disabled (or some of the supported languages are unavailable), please check system TTS settings.

				On Android voice instructions are available in 27 languages: English, Arabic, Chinese (Traditional and Simplified), Czech, Danish, Dutch, Finnish, French, German, Greek, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Persian, Polish, Portuguese, Romanian, Russian, Spanish, Thai, Turkish, Ukrainian, Vietnamese.

biodranik (Migrated from github.com) commented

2023-02-11 21:31:54 +00:00

Outdated

content/faq/index.md

					
				@ -0,0 +104,4 @@

				Google TTS supports all listed languages except of Arabic and Persian (Farsi). For these languages you may need to install third party TTS (for example, eSpeak TTS, Vocalizer TTS or SVOX Classic TTS) and a language pack from app store (Google Play Store, Galaxy Store, etc).

				On iOS voice instructions are available in 26 languages: English, Arabic, Chinese (Traditional and Simplified), Czech, Danish, Dutch, Finnish, French, German, Greek, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Polish, Portuguese, Romanian, Russian, Slovak, Spanish, Swedish, Thai, Turkish.

biodranik (Migrated from github.com) commented

2023-02-11 21:32:15 +00:00

Ditto

rtsisyk commented

2023-02-12 05:18:52 +00:00

It's hard to sync and add new sections in one large file.

FAQ is easier to support if it will be split to subsections, each with its own page for each entry. It simplifies the addition/translation of a new item and allows to add more images to any item if necessary (think about TTS or small animations about a feature). Also, keeping separate subpages with images will help to avoid overbloating of the index page that can have only titles of the subpages for example.

I already have a list of 50+ items for FAQ.

A structure similar to News can be used.

Ok, I will split.

> It's hard to sync and add new sections in one large file. > > FAQ is easier to support if it will be split to subsections, each with its own page for each entry. It simplifies the addition/translation of a new item and allows to add more images to any item if necessary (think about TTS or small animations about a feature). Also, keeping separate subpages with images will help to avoid overbloating of the index page that can have only titles of the subpages for example. > > I already have a list of 50+ items for FAQ. > > A structure similar to News can be used. Ok, I will split.

biodranik commented

2024-06-13 22:14:02 +00:00

(Migrated from github.com)

Closing it in favor of #242