View Issue Details

IDProjectCategoryView StatusLast Update
0005047Talerdocumentationpublic2017-06-06 12:18
ReporterMarcello Stanisci Assigned ToMarcello Stanisci Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityurgentSeveritytextReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.3Fixed in Version0.3 
Summary0005047: reorganizing content
DescriptionThe 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.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Marcello Stanisci

2017-05-31 07:17

reporter   ~0012195

Last edited: 2017-05-31 07:18

What if we use the 'landing' repo to host some index.html for all the documentation?
This way, each part does its proper job - namely the api repo doesn't have to now links
about other documentation parts that have nothing to do with 'api'.

After all, docs.taler.net *is* a landing page (for documentation).

Christian Grothoff

2017-05-31 07:37

manager   ~0012196

Yes, landing/docs/index.html would seem like a good place.

Maybe move the existing landing logic to landing/demo/.

Christian Grothoff

2017-05-31 07:38

manager   ~0012197

Oh, and maybe do support i18n, just like the existing landing logic, so index.html.j2...

Marcello Stanisci

2017-06-02 16:58

reporter   ~0012208

/api setup, paths beginning with /_static give 404.

Marcello Stanisci

2017-06-05 19:39

reporter   ~0012232

The homepage (and all nginx routes) is (are) there. What's missing is: i18n and some fancier styling for it.

Please NOTE that the buildbot worker for docs updating is still open issue.

Christian Grothoff

2017-06-05 20:59

manager   ~0012233

Filed the remaining issues as 0005067.

Issue History

Date ModifiedUsernameFieldChange
2017-05-30 12:46Marcello StanisciNew Issue
2017-05-30 12:46Marcello StanisciAssigned To => Marcello Stanisci
2017-05-30 12:46Marcello StanisciStatusnew => assigned
2017-05-30 15:22Marcello StanisciDescription Updated
2017-05-31 07:17Marcello StanisciNote Added: 0012195
2017-05-31 07:18Marcello StanisciNote Edited: 0012195
2017-05-31 07:37Christian GrothoffNote Added: 0012196
2017-05-31 07:38Christian GrothoffNote Added: 0012197
2017-06-01 20:55Christian GrothoffSeverityminor => text
2017-06-02 16:58Marcello StanisciNote Added: 0012208
2017-06-04 19:18Christian GrothoffPrioritynormal => urgent
2017-06-04 19:18Christian GrothoffProduct Version => git (master)
2017-06-04 19:18Christian GrothoffTarget Version => 0.3
2017-06-05 19:39Marcello StanisciNote Added: 0012232
2017-06-05 20:59Christian GrothoffNote Added: 0012233
2017-06-05 20:59Christian GrothoffStatusassigned => informing
2017-06-05 20:59Christian GrothoffResolutionopen => fixed
2017-06-05 20:59Christian GrothoffFixed in Version => 0.3
2017-06-06 12:18Christian GrothoffStatusinforming => closed