-
I created documentation in asciidoc format.
As I look at it in preview mode all looks good, however generated results using simple shell script are not so good.
%wojtek Could you look at this issue?
%kobit Where we should put generated documentation? For now project is not public.
-
We should put them where our rest documentation is: http://docs.tigase.org
I know the project is not public yet but it will be public.
-
Linked image files lacked width specification therefore weren't sized properly - I've added those.
In addition I've mavenized documentation section so it will be easier to build the whole documentation using jenkins and include on http://docs.tigase.org (v. http://docs.tigase.org/tigase-swift/snapshot/Tigase_Swift_Guide/html/).
Jenkins job were created as well: http://build.tigase.org/jenkins/job/private-tigase-swift-documentation/
-
This looks good to me. It's a good starting point. I think we can add more content when we receive a specific questions from users/developers. So instead of answering questions you will simply add the information to the documentation. This way we will have documentation with content which is really useful to people.
By the way, is there a syntax coloring feature in the asciidoc?
-
Andrzej Wójcik wrote:
so I suppose there is no support for coloring code in Swift - maybe no markup parser?
This depends on the highligher used, vide: http://asciidoctor.org/docs/user-manual/#source-code-blocks . Looking at documentations of source-highlighter only highlight.js seems to mention swift.
Type |
Task
|
Priority |
Normal
|
Assignee | |
RedmineID |
4235
|
Prepare documentation for developers containing informations how to use TigaseSwift library.