-
Ah, one day. And it will include example data outputs for handy reference. Maybe even be built with [pweave](http://mpastell.com/pweave/) or [stitch](https://pystitch.github.io/) to make including the…
-
The source for API documentation is located in the [main repo](https://github.com/home-assistant/home-assistant/tree/dev/docs).
Suggestion to move it and make it available at developers.home-assist…
-
Create documentation for API v6
-
It would be best practice when adding changes to the API to always document the features and how the running of the API works to minimize build errors of new code.
This also helps us when building…
-
First off, thanks for an amazing product.
Is there any generic documentation on the server API? I'm sure people (myself included) would love to write their own clients for WeMessage that wasn't lim…
-
Update our API Docs Wiki to be more reflective of what we actually have. This should help steer future development on the backend to see what we have missing.
-
Fill out technical user documentation.
Current draft at https://gist.github.com/R2ZER0/4170adb28bd6946cf7f10ed0baf869d5
Sections:
- [x] Introduction
- [x] Notes & Best Practices
- [x] Endpoints
- [x]…
-
At the moment, the most up-to-date documentation lives on the static landing page for KEVin.
In reality, there should also be a central place for seeing endpoints and what they do. I.E. Swagger-UI.
-
I want to use depth map through the API, can you explain how to use it?
-
Currently we have Doxygen set up, but not the graphs since they take hours to generate.
The API displayed in other projects such as pybind11 seems very nice, so may be worthwhile to look at what the…