Now to test changes I need to mod empty-game template or the-question and after test revert it.
Now to learn Rakugo you must read docs, or read scripts in the-question, but it can be not enough.
So to do it test faster and esier and learn easier we need tutorial/test.
It will work simliar to tutorial included in Ren'Py SDK.

Add either a section to the README.rst or a new file with all the info needed to start contributing, i.e., which code formatting are you using, which linter, the testing process, etc.

Do you have a favorite TV show, movie, computer game or band ?
Do you like music, flags or special occasions ?
Do you think there is a logo or logo category that is missing from our awesome logo collection ?

Please use this GitHub issue to request a new logo from the team 👍 🌮

![fuchsia-logos-tribute-selection](https://user-images.githubusercontent.com/418747/75613050-20ee2280-5b75-11e

• Add who and how (Issue) needs to be contacted at the zofar-team
• request at an early stage, preferably even before the other work on the SUF is started
• consider Zofar sprints
• add a template for what zofar needs (dzhw/zofar#333 (comment))
• add, that and why we use pages and why (not) questions
• atm (still? ask Christ

Steps to reproduce it

1. go to https://docs.readthedocs.io/en/latest/
2. click on search
3. type configuration
4. hit Enter

Actual result

You are redirected to https://docs.readthedocs.io/en/latest/search.html?q=configuration&check_keywords=yes&area=default which is the default search (instead of the Search As You Type)

Expected result

I was expecting that it will j

From italia/docs.italia.it#447:

The current style of bullet points is an arrow pointing right which looks exactly like an expanding arrow

I have to resist the urge of clicking it every single time to reveal more content.

Currently only the desktop section has a getting started document.

If the docs are meant to be also step-by-step instructions, it would be nice if such documents also exist for the mobile applications to give the user a starting point into the software.

This is the repo that the doc is pointing.

The installation guild in the repo(readme.md) is different from the one in docs. Any comments?

The motivation is that I'm having GitHub App integration enabled for the whole org.
But I want to prevent bot spamming with config reminders to irrelevant repos. Like a repo with gh-pages hosted static website.

Using #8 I found that if you click in the main top-left-title link you go to /default-language/default-version. I think this is because of the pathto being overriden.

Although, we should find a way to make only that link points to the top level of the current version.

I think that Sphinx 2.0 needs this selector:

versionwarning_body_selector = 'div[itemprop="articleBody"]'

while with Sphinx < 2.0 we were using:

versionwarning_body_selector = 'div.body'

So, it would be good to set the proper default based on the Sphinx version.

Ligato Docs currently contain 3 articles named KVScheduler just in the navbar.

• Tutorials - https://docs.ligato.io/en/latest/tutorials/05_kv-scheduler/
• Plugins - https://docs.ligato.io/en/latest/plugins/kvs-plugin/
• Dev Guide - https://docs.ligato.io/en/latest/developer-guide/kvscheduler/

The last two seem to have started from same article, but now they are clearly very different d