docs: add MkDocs documentation #1312
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eglitise
added
documentation
| If using a standalone Appium server, make sure the server also has the necessary | ||
| [driver(s)](https://appium.io/docs/en/latest/ecosystem/drivers/) for your target platform(s)! | ||
|
|
||
| While the Inspector is designed to work with Appium 2, it is also compatible with |
There was a problem hiding this comment.
Not sure if we even need to mention Appium 1 except of the fact it has been EOLed a while ago
There was a problem hiding this comment.
I think it's reasonable to mention here, given that most things in the Appium ecosystem are no longer compatible with Appium 1. There will still be a point where Appium 1-specific workarounds (such as automationName not being guaranteed) will be dropped, and the docs updated accordingly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a fully comprehensive documentation for the Inspector. It covers things like quickstart & installation, troubleshooting, contributing guidelines, and of course, descriptions for every bit of functionality in the GUI. Also included are CI workflows for PRs and publishing.
The README will be updated in a separate PR.
Resolves #1105.