Documentation Improvement Suggestions

A couple of ideas for how to improve the ABRP documentation:

1. Add a section on “driving the plan”

2. Add a section of “ABRP nomenclature” — things like giving the names ABRP uses for UI elements, settings, and common tasks. That would both make it easier to explain how things work & to communicate to developers when there are bugs / questions / feature requests.

3. Add UI documentation. There is a lot of information displayed “implicitly” — it would be really helpful to have a collection of labeled screen captures explaining what you are seeing. For example on iOS the “action tiles” (driving directions) seem to have a black background when the tile is a “for your information only — no action required” (continue straight for 30 miles) and a blue background when the tile is displaying the next maneuver (take exit 123). But I don’t know this, I’m guessing that that is what the difference in background color means & I’ve learned it over time by inference, and I made some incorrect guesses along the way… A place where this would be particularly helpful is with the “next stop” tile, especially when the stop is a charging station. Especially since there is such a very wide range in the availability of real-time information & in the potential meanings.

4. In each section provide a list of “common tasks” or even organize the sections around common use cases. For example, “Find the closest bathroom.”

5. It would be really nice to have an option in the online manual to include features that are planned or under development along with a way to indicate how important they are to you.