diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 1af2c5cccc..d1810c8ae3 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -79,7 +79,7 @@ You can also help to keep the OpenStreetMap wiki **up-to-date** for StreetComple
If you would like to help and are able to contribute code, you are most welcome.
-There are many reasonable feature requests and ideas for new question types in the issue tracker which you can use. If you have own ideas on how to improve this app and want to make sure that the pull request will be merged, it is strongly suggested you **open an issue first** to discuss the feature, especially if you aim to add a new quest, [see below](#developing-new-quests).
+There are many feature requests and ideas for new question types in the issue tracker which you can use. If you have own ideas on how to improve this app and want to make sure that the pull request will be merged, it is strongly suggested you **open an issue first** to discuss the feature, especially if you aim to add a new quest, [see below](#developing-new-quests).
Note that StreetComplete also uses [some dependencies](#issues-with-dependencies), where contributions are likely also accepted and help StreetComplete, too.
@@ -96,6 +96,8 @@ In case you **don't have an idea of a quest?** Look [at the existing issues](htt
Always remember to pay attention to [the quest guidelines](https://github.com/streetcomplete/StreetComplete/blob/master/QUEST_GUIDELINES.md) of StreetComplete! It also has tips for implementing a quest.
+See also [this far more detailed guide to making a new quest](CONTRIBUTING_A_NEW_QUEST.md).
+
### Code style
Inheritance and class hierarchy should be avoided if possible. It is preferable to extract shared code to helper file such as [KerbUtil.kt](app/src/main/java/de/westnordost/streetcomplete/osm/kerb/KerbUtil.kt).
diff --git a/CONTRIBUTING_A_NEW_QUEST.md b/CONTRIBUTING_A_NEW_QUEST.md
new file mode 100644
index 0000000000..dcde615e39
--- /dev/null
+++ b/CONTRIBUTING_A_NEW_QUEST.md
@@ -0,0 +1,522 @@
+This file describes in detail the process of creating a new quest.
+
+For code style and more general info - see [CONTRIBUTING file](CONTRIBUTING.md#development).
+
+If you want to contribute code to StreetComplete, then making a new quest is one of the easiest programming tasks. It is quite easy to implement a quest where layout design matches an existing quest. For example one more yes/no quest or where user taps one of displayed images.
+
+Contributions like that are highly welcomed and you would make mapping one more thing in OSM much easier! You can implement it also if you never used Kotlin or implemented anything for Android. Being highly experienced programmer is not necessary here.
+
+Reading the text below is not necessary to create a new quest. Duplicating an existing quest and modifying its code may be sufficient - people were creating new quests before this documentation existed. This material simply helps you get a better understanding of it.
+
+# Dependencies - initial setup
+
+- install necessary software ([Android Studio](https://developer.android.com/studio) and [git](https://git-scm.com/downloads))
+- create a GitHub [account](https://github.com/signup) if needed
+- visit [https://github.com/streetcomplete/StreetComplete](https://github.com/streetcomplete/StreetComplete) and press the "fork" button on the top right
+ - this creates a copy of StreetComplete repository that you control and can prepare code there
+- clone your fork of a StreetComplete repository
+ - in Android Studio it can be achieved without command line ( File -> New -> Project from Version Control... )
+ - see [Github Documentation](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) how repository can be cloned and where its URL can be found
+- open StreetComplete in Android Studio
+- [setup an emulator in Android Studio](https://developer.android.com/studio/run/emulator#install) (you can also [connect to a real device via USB](https://developer.android.com/studio/run/device), this can replace using the emulator)
+- run StreetComplete in the emulator (to verify that everything was setup as required)
+
+If you are doing it for the first time, don't worry if there is an error to solve along the way, this is typical for setting up an Android development environment. See [CONTRIBUTING file](CONTRIBUTING.md#development) which has some links to information about the setup.
+
+# Invent a new quest
+
+## Own ideas
+
+To [repeat](CONTRIBUTING.md#developing-new-quests) from that documentation file: [**open an issue** discussing the quest](CONTRIBUTING.md#developing-new-quests), before starting other work. This way it can be confirmed that such quest can be included. This can be skipped if you are an [experienced](https://github.com/streetcomplete/StreetComplete/discussions/3450) StreetComplete contributor.
+
+## Existing proposals
+
+You can also look at [quest proposals waiting for implementation](https://github.com/streetcomplete/StreetComplete/issues?q=is%3Aissue+is%3Aopen+label%3A%22new+quest%22+-label%3A%22blocked%22).
+
+# Prepare repository for development
+
+That is a good moment to create a branch and switch to it.
+
+It can be done using Android Studio GUI (Git -> New branch...), or in CLI with the following command:
+
+```bash
+git checkout -b short_branch_name_describing_planned_work
+```
+
+In general, [Intellij documentation](https://www.jetbrains.com/help/idea/using-git-integration.html) about git integration is applicable to Android Studio (which is rebranded Intellij with minor modifications).
+
+# Learn from existing code
+
+## Find a base
+
+### Hints for looking around code
+
+Full text search ([ctrl+shift+f](https://www.jetbrains.com/help/idea/finding-and-replacing-text-in-file.html) is always useful.
+
+Use Ctrl+N to go to a certain class. Ctrl+ mouseclick on a function, class, etc. leads to where it is defined.
+
+Use Ctrl+Q (but not on MacOS 😉) after having marked a class, symbol or function to display the documentation for it.
+
+With Ctrl+Shift+A you can find and explore **any** action you can do in Android Studio (try it by typing for example "go to").
+But "Find usages" (alt+F7) is also a very powerful way to find where given function/constant/property/etc is appearing, classified by usages.
+
+### Base on existing
+
+Base the new quest on one that exists already.
+
+Find one that has the same type of interface as the one that you are trying to implement.
+
+Are you trying to implement a quest that will have simple yes/no answer? Take [`AddIsDefibrillatorIndoor`](app/src/main/java/de/westnordost/streetcomplete/quests/defibrillator/AddIsDefibrillatorIndoor.kt) quest as a base. Or [`AddTracktype`](app/src/main/java/de/westnordost/streetcomplete/quests/tracktype/AddTracktype.kt) where the mapper will be selecting one of presented images.
+
+Is it going to be asked for POIs and should be disabled by default? [`AddWheelchairAccessBusiness`](app/src/main/java/de/westnordost/streetcomplete/quests/wheelchair_access/AddWheelchairAccessBusiness.kt) may be a good base.
+
+Quests are grouped in [one folder](app/src/main/java/de/westnordost/streetcomplete/quests).
+
+Implementing quest by duplicating and modifiying existing one is the recommended method.
+
+### Locating a quest
+
+Search across the code for part of a question or other text specific to this quest. For example "the name of this place?".
+
+You will find an [XML file](app/src/main/res/values/strings.xml) with an entry looking like this:
+
+```xml
+ "What’s the name of this place?"
+```
+
+The identifier `quest_placeName_title` is a string reference, used in the code to allow translations.
+
+Search for this identifier in `*.kt` files, it should appear in the quest file (in this case [AddPlaceName.kt](app/src/main/java/de/westnordost/streetcomplete/quests/place_name/AddPlaceName.kt)).
+
+This method can often be used to locate relevant code.
+
+### Other people
+
+The issue proposing a quest may also contain hint which quests are similar. If you are unsure what would be a good base - you can ask in issue discussion to confirm what you found or ask for help in finding a good base for a given issue.
+
+## Pull Requests
+
+One of the better ways to get around a codebase that is new to you is to look at recent accepted proposals to change the code (pull requests).
+
+This is also likely useful here.
+
+Find some [recent ones](https://github.com/streetcomplete/StreetComplete/pulls?q=is%3Apr+is%3Aclosed) adding a quest.
+
+You can look at what was changed to achieve the goal, where relevant code is located. How much coding was needed to implement something? And what kind of comments are typical, how long one needs to wait for maintainers and so on.
+
+This can be also used to locate relevant code, especially helpful if some change needs to be done in multiple files.
+
+# Copying
+
+Duplicate the relevant quest folder from [`app/src/main/java/de/westnordost/streetcomplete/quests`](app/src/main/java/de/westnordost/streetcomplete/quests). Some contain multiple quests, in such case delete unnecessary files.
+
+Some quests are entirely defined in a single file, some have additional answer class, custom interface or utility classes.
+
+For example, lets imagine that new quest will ask whether [AED](https://wiki.openstreetmap.org/wiki/Tag:emergency%3Ddefibrillator) is placed indoor or outdoor. A very similar in mechanics quest with simple yes/no question is for example [quest asking "Is this bicycle parking covered (protected from rain)?"](app/src/main/java/de/westnordost/streetcomplete/quests/bike_parking_cover/AddBikeParkingCover.kt).
+
+So, as the first step: lets copy [`app/src/main/java/de/westnordost/streetcomplete/quests/bike_parking_cover/`](app/src/main/java/de/westnordost/streetcomplete/quests/bike_parking_cover) folder into `app/src/main/java/de/westnordost/streetcomplete/quests/defibrillator/`.
+
+This is done in [this commit](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/7d9ad571f521055a4c5a0006743762fd16e4c9d6) in the demonstration repository.
+
+# Adjust the copy
+
+After the quest is copied it is necessary to adjust it a bit so it is not a duplicate anymore.
+
+Change its class name and the file name to the new one.
+
+In copied code change package info (things like `package de.westnordost.streetcomplete.quests.defibrillator` at the top) to match the new folder containing the quest.
+
+When commiting changes be careful to not change already existing quest - only new code (using built-in refactoring rename will affect also `QuestsModule.kt` entry for an existing quest).
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/9c65d00c7d096c3fee61650e1465a43b7e7f5712) in the example repository.
+
+# Add the quest to the list of active ones
+
+Adjust [QuestsModule.kt](app/src/main/java/de/westnordost/streetcomplete/quests/QuestsModule.kt) file. It contains a big list of active quests, ordered by priority. Read [what governs their priority](https://github.com/streetcomplete/StreetComplete/blob/master/app/src/main/java/de/westnordost/streetcomplete/quests/QuestsModule.kt#L172-L195) but do not worry too much, it can be tweaked later.
+
+Add your quest to the list so that it will be loaded by the app.
+
+As this point you can run the app in emulator - everything should work and one of quests will appear twice.
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/b4f01eeb752f92fd6927fbb9a943ea19a4799eec) in the example repository.
+
+# Modify the template
+
+At this point prepared template can be modified to achieve the intended effect.
+
+See for example [simple yes/no quest asking whether AED is indoor or outdoor](app/src/main/java/de/westnordost/streetcomplete/quests/defibrillator/AddIsDefibrillatorIndoor.kt).
+
+## Element selection
+
+`elementFilter` property defines nodes, ways and relations which will be selected for a given quest. It is an element selection used by OsmFilterQuestType.
+
+```kotlin
+ override val elementFilter = """
+ nodes with
+ emergency = defibrillator
+ and access !~ private|no
+ and !indoor
+ """
+```
+
+This query will be limited to object which fulfill some requirements.
+
+- `nodes with`
+ - nodes only, ways and relations are not eligible
+- `emergency = defibrillator`
+ - this tag must be present
+- `and access !~ private|no`
+ - and `access` tag must not have values `private` or `no` (the `~` indicates it is a [regular expression](https://en.wikipedia.org/wiki/Regular_expression) which will be matched against the whole string)
+ - this filter excludes objects where mapper will likely has no access necessary for survey
+- `and !indoor`
+ - and `indoor` key must not be present at all, to show only ones where this tag is still missing
+
+See the documentation of [`ElementFilterExpression`](https://github.com/streetcomplete/StreetComplete/blob/master/app/src/main/java/de/westnordost/streetcomplete/data/elementfilter/ElementFilterExpression.kt) for a complete documentation of the syntax. You can look around some quests to see more examples of such element filter expressions.
+
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/2726ff1c7b3121825e808c4566e6e534392121b3) in the example repository.
+
+### Prototyping
+
+[Overpass Turbo](http://overpass-turbo.eu/) has own syntax but it is very useful tool for prototyping filters. It is very useful to verify own assumptions how things are tagged. Especially in more complex cases.
+
+### Hints
+
+The rules should generate as few false positives as possible. I.e. instead of asking for the surface of any way tagged with `highway=*`, the surface should instead only be asked for an inclusive list of roads.
+
+In some cases it will be a good idea to [limit quests to certain countries](#enabledInCountries).
+
+You can obtain more info about properties by placing the cursor in a property and pressing Ctrl+Q within Android Studio.
+
+## changesetComment
+
+```kotlin
+override val changesetComment = "Add whether defibrillator is inside building"
+```
+
+message used as a changeset comment
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/0db8827133b07ce32c3c1287604198efeabc7bf6) in the example repository.
+
+## wikiLink
+
+```kotlin
+override val wikiLink = "Key:indoor"
+```
+
+points to the OSM Wiki page most relevant to the given quest, typically it is an added key. In this case, it is a page about [indoor=* tagging](https://wiki.openstreetmap.org/wiki/Key:indoor).
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/13ec6b97b52413cf09f3b71311b877b746d29576) in the example repository.
+
+## icon
+
+```kotlin
+override val icon = R.drawable.ic_quest_defibrillator
+```
+
+icon drawable, you can initially use any icon.
+
+Do not worry, submissions with placeholder icons are also welcomed! In many cases icon itself was not made by the PR author.
+
+More info about icon handling [will be given later](#adding-quest-icon).
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/7cecce384a5baf365119fd3453d600a87f87fadb) in the example repository.
+
+## questTypeAchievements
+
+```kotlin
+override val questTypeAchievements = listOf(LIFESAVER)
+```
+
+In quest achievements, list what is relevant to the given quest, see the full list of available ones in [AchievementsModule.kt](app/src/main/java/de/westnordost/streetcomplete/data/user/achievements/AchievementsModule.kt)
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/f043440b43ad84d321c7aae4fd03095c34af8eb4) in the example repository.
+
+## getTitle
+
+```kotlin
+override fun getTitle(tags: Map) = R.string.quest_is_defibrillator_inside_title
+```
+
+It is a message displayed to user, code here passes a [reference](https://developer.android.com/guide/topics/resources/string-resource) to the string. You can change it to the new, not yet existing one and use a built in tool to place text.
+
+Actual strings sit in [app/src/main/res/values/strings.xml](app/src/main/res/values/strings.xml)
+
+There are separate files with translated text, but do not worry about it - [translations are handled separately](CONTRIBUTING.md#translating-the-app).
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/5fe2b8149b25ac375a09a45ad949dc804d687825) in the example repository.
+
+## Form
+
+```kotlin
+override fun createForm() = YesNoQuestAnswerFragment()
+```
+
+Form defines interface used by mappers.
+
+In this case, the simplest possible is used.
+
+But sometimes more complex ones are needed, see for example [AddBridgeStructure.kt](https://github.com/streetcomplete/StreetComplete/blob/master/app/src/main/java/de/westnordost/streetcomplete/quests/bridge_structure/AddBridgeStructure.kt)
+
+`override fun createForm() = AddBridgeStructureForm()`
+
+With form defined in [AddBridgeStructureForm](app/src/main/java/de/westnordost/streetcomplete/quests/bridge_structure/AddBridgeStructureForm.kt)
+
+## applyAnswerTo
+
+```kotlin
+override fun applyAnswerTo(answer: Boolean, tags: Tags, timestampEdited: Long) {
+ tags["indoor"] = answer.toYesNo()
+}
+```
+
+This code is responsible for modifying `tags` object (passed by reference).
+
+In this case it would set `indoor` tag to have either `yes` or `no` answer, depending on selection in the quest interface.
+
+Actions may include (examples from various quests):
+
+- `tags["indoor"] = answer.toYesNo()`
+ - set `indoor` tag to have either `yes` or `no` answer, based on provided data
+- `tags.remove("amenity")`
+ - remove key if it is present
+- `tags.updateWithCheckDate("lit", answer.toYesNo())`
+ - if the new value differs from existing tag value: new value will be applied
+ - in case of value being the same: add survey date tag, it would be `check_date:lit=` in this case
+ - so can be used even if value will stay the same - possible for resurvey quests
+ - if the new value is the same as existing tag value: adds survey date tag (`check_date:lit=` in this example)
+ - always update survey tag if present already
+ - necessary if given quest includes resurvey of old elements that are already tagged
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/04aa86351a9b3634a7a0e034e47936b2c4e17f9b) in the example repository.
+
+## Extras
+
+Info listed so far must be supplied by every quest. But there are also several optional fields. This specific quest has
+
+```kotlin
+override fun getHighlightedElements(element: Element, getMapData: () -> MapDataWithGeometry) =
+ getMapData().filter("nodes with emergency = defibrillator")
+```
+
+which causes nearby `emergency = defibrillator` nodes to be shown (icons used are defined in [PinIcons.kt](app/src/main/java/de/westnordost/streetcomplete/screens/main/map/PinIcons.kt))
+
+See [also other optional properties](app/src/main/java/de/westnordost/streetcomplete/data/osm/osmquests/OsmElementQuestType.kt).
+
+See [this step](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/1d648e56562d16a5dc3588ca7de8558f97d5919a) in the example repository.
+
+Note that for this quest one extra property present in the original quest used as a template [was removed](https://github.com/matkoniecz/StreetComplete_quest_creation_tutorial/commit/a9fd3efe96cbc6241b3b0f65d4a2be27f1c6afb8)
+
+# Adding quest icon
+