-
The Doxygen-generated documentation pages are insufficient. The following needs to be done:
- [x] Easier navigation (see https://code.google.com/p/bwapi/wiki/OldDocumentation vs http://bwapi.github.io…
-
Heyo,
Over the last few months of using m.css I've been working on a 'post-process' script to do some further work on the generated html, and now it's polished enough that I figure you might apprec…
-
At present, there is only one api document, which is difficult to read.
No collapsing, no functional navigation.
Can you introduce the functions of each series of APIs separately? as a separate page
-
status NEEDINFO severity *normal* in component *general* for *---*
Reported in version *1.8.13* on platform *Other*
Assigned to: Dimitri van Heesch
On 2017-01-18 18:57:45 +0000, Corentin Séchet wrot…
-
I'm using the great style almost everywhere. I'm shipping this style simply with the library, because I don't like submodules. Keeping the style up-to-date is in issue however. We had a really nice co…
-
In GitLab by @pdamme on Mar 17, 2021, 19:40
The documentation of the prototype should ideally reside in a top-level directory `doc`. We need to set up the processes to generate the qualifying parts o…
-
ecTrans currently has no documentation beyond the relevant chapter of [the IFS documentation](https://www.ecmwf.int/en/elibrary/81372-ifs-documentation-cy48r1-part-vi-technical-and-computational-proce…
-
- [ ] The process of generating the docs with doxygen itself should be documented. [Probably here](https://nubook.nubots.net/guides/general/documentation#page-content) or somewhere near that.
- [ ] U…
-
**Description**
Currently there are 2 open PRs suggesting documentation builders:
- #2672
- #2478
- #2710
I believe that is a valuable feature, but I believe it's missing RTD suppott that wo…
-
My goal is to go C++ source > doxygen > breathe > sphinx (with sphinx-markdown-builder) to produce markdown output. I am trying to run *sphinx-markdown-builder* with rst files containing [breathe](htt…