we will be providing an API for each part of our code which a 3rd party script can interact with. our frontend provides an API which people can develop their extensions using its power. our frontend API also provides platform specific functionalities it means a 3rd party developer can write an extension which behaves differently in different platforms. in addition to this API obviously our "UnifiedHandler" also provides a nice API which we ourselves are using it in frontend.
what we want in this issue
think of a standard way to write and maintain documentations for our APIs.
this issue doesnt include writing documentations on how to use our application. its only about how developers can use our APIs. those how-to-use docs are maintained in "promotion" project here in this repo.
what we have now
we will be providing an API for each part of our code which a 3rd party script can interact with. our frontend provides an API which people can develop their extensions using its power. our frontend API also provides platform specific functionalities it means a 3rd party developer can write an extension which behaves differently in different platforms. in addition to this API obviously our "UnifiedHandler" also provides a nice API which we ourselves are using it in frontend.
what we want in this issue
think of a standard way to write and maintain documentations for our APIs.