Open MobsyaBot opened 6 years ago
Comment by stephanemagnenat Monday Jan 15, 2018 at 19:41 GMT
I agree with using reStructurdedText, I reached the same conclusion.
Regarding content, indeed we need to do clean-up. This can be a team effort, and we can coordinate from this issue. However, it would be good not to delay this too long as the offline doc is currently out of date and this is getting worst with every release.
I agree about starting from the language/APIs.
Comment by cor3ntin Tuesday Jan 16, 2018 at 10:25 GMT
First file uploaded https://github.com/cor3ntin/aseba/blob/clean_doc/doc/aseba-language.rst
Comment by stephanemagnenat Tuesday Jan 16, 2018 at 10:58 GMT
First file uploaded https://github.com/cor3ntin/aseba/blob/clean_doc/doc/aseba-language.rst
The table Expressions and assignments has formatting errors.
Comment by cor3ntin Wednesday Jan 17, 2018 at 09:43 GMT
The native functions are all done. Unfortunately, github does not support maths formula so you won't see the file properly, but it will works fine on readthedocs https://github.com/cor3ntin/aseba/blob/clean_doc/doc/aseba-std-natives.rst
Comment by cor3ntin Wednesday Jan 31, 2018 at 08:44 GMT
There are a few questions regarding the docs that readthedocs does not solves
If so, is read the doc the right place ? Maybe we could have a git repo dedicated to generated / transformed docs served on github.io
Comment by stephanemagnenat Wednesday Jan 31, 2018 at 08:54 GMT
These are good points! My feeling:
Comment by cor3ntin Wednesday Jan 31, 2018 at 09:03 GMT
I was not suggesting that doxygen be replaced; It's more about
Being curious, I looked up what existed and Doxygen is probably still our best bet. There is this project https://github.com/sourcey/moxygen that transforms Doxygen output to markdown I we want.
Comment by stephanemagnenat Wednesday Jan 31, 2018 at 09:17 GMT
The question of where to put the generated doxygen documentation is indeed always annoying. We could actually put them within each release, along with the binaries, what do you think?
Comment by cor3ntin Wednesday Jan 31, 2018 at 09:21 GMT
I tend to look for documentation online, so I would expect to find it on readthedocs ( or equivalent ) in html form- but that may well be a very personal preference.
Comment by stephanemagnenat Wednesday Jan 31, 2018 at 09:23 GMT
I see your point, it would be nice to have it on readthedocs, but we really do not want to commit it in the repository. I did it for Dashel and I feel it is a bad idea.
Comment by stephanemagnenat Wednesday Jan 31, 2018 at 09:25 GMT
I added the proposed structure at the top of this issue.
Comment by stephanemagnenat Tuesday Feb 06, 2018 at 09:58 GMT
@cor3ntin could you please briefly document the migration process, so that third parties could help?
Issue by cor3ntin Monday Jan 15, 2018 at 17:46 GMT Originally opened as https://github.com/aseba-community/aseba/issues/780
I'm in the process of moving some of the documentation from https://www.thymio.org/en:start to github and readthedocs. My initial goal was to use markdown but I'm reconsidering that choice and will use reStructuredText instead, which will work best for documenting APIs especially since there are some maths formulas. The process is unfortunately not automatic - at least not full and there is a lot of clean up to do, both because formatting issue and outdated content.
I suggest we keep the "outdated" information where they are and focus on what's relevant to 1.6+. We should spread the efforts over several weeks or months since it's quite tedious and there are more pressing matters. I think I will focus on the language/apis first since there are no questions regarding the content and move from there.
Added by @stephanemagnenat: As pointed out by @cor3ntin, we need to come with a structure for the documentation to be put on readthedocs. Here is what I propose:
Aseba
Targets
Not all these need to be added at once, but we should agree on the structure as soon as possible.