That’s a fair point. Automatically generated FORD docs can be thought of more as a technical documentation of the code, which is different from documentation in the sense of user manuals (as the term “documentation” is often used). @loiseaujc already pointed to more of a manual-style documentation, but it will require some update for more end-user accessibility eventually (as pointed out in the TODO). What may ultimately help with that is the better integration of FORD and sphinx.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Thank you to the Fortran-lang community | 0 | 234 | July 8, 2024 | |
The Fortran stdlib project has garnered over 1000 stars on GitHub!
|
6 | 635 | July 2, 2024 | |
New Fortran-lang paper | 5 | 731 | September 17, 2021 | |
Add FPM topic/mini book to the Fortran lang website? | 2 | 192 | January 22, 2025 | |
GSoC 22: fpm-ize the Fortran Ecosystem || Blog Post by Arteev Raina || #16 | 0 | 393 | September 11, 2022 |