View Revisions: Issue #5047

Summary 0005047: reorganizing content
Revision 2017-05-30 17:22 by Marcello Stanisci
Description The non RESTful API Sphinx code must be spread into the following manuals:
(and possibly other content should be killed)

* exchange/auditor operator manual
* merchant backend operator manual
* merchant frontend tutorials
* wallet developer
* "onboarding" documentation - deployment instructions

All the documentation is available from a unique entry point: docs.taler.net.

This entry point then will have the following paths:

/api - RESTful API
/wallet - wallet developer manual
/merchant/backend - merchant backend operator manual
/merchant/frontend/<LANG> - merchant frontend tutorial for language <LANG>
/exchange - exchange operator manual
/onboarding - deployment, onboarding, etc.
/code/<COMPONENT> - <COMPONENT>'s HTMLized doxygen

NOTE1 api.taler.net should redirect to docs.taler.net
NOTE2 make exhcange's doc/taler-exchange.texi and doc/manual/manual.texi *one* file.
Revision 2017-05-30 14:46 by Marcello Stanisci
Description
The non RESTful API Sphinx code must be spread into the following manuals:
(and possibly other content should be killed)

* exchange/auditor operator manual
* merchant backend operator manual
* merchant frontend tutorials
* wallet developer
* "onboarding" documentation - deployment instructions

All the documentation is available from a unique entry point: docs.taler.net.

This entry point then will have the following paths:

/api - RESTful API
/wallet - wallet developer manual
/merchant/backend - merchant backend operator manual
/merchant/frontend/<LANG> - merchant frontend tutorial for language <LANG>
/exchange - exchange operator manual
/onboarding - deployment, onboarding, etc.
/code/<COMPONENT> - <COMPONENT>'s HTMLized doxygen

Lastly, api.taler.net should redirect to docs.taler.net