Generate Infusion Framework API docs from the source code using infusion-tags
Description
Environment
Activity
Justin Obara July 31, 2024 at 6:10 PM
There hasn’t been much traction on this for a while and our doc site runs independently at the moment. If we want to switch back to something automated we may want to do it from the docs site side and use 11ty to generate the docs from an infusion build.
Anastasia Cheetham December 10, 2015 at 4:10 PM
Given the changes made to the docs for , do you thing we should close this issue (and FLUID=5329) as "won't do"?
Antranig Basman October 13, 2015 at 8:31 PM
I had a look at the tool and from where I am this evening, it looks like it will be too much work to adapt it to produce what we want. We would like i) for it to produce markdown, not HTML, and also it currently makes no attempt to parse our JavaDoc-inspired doc comments. This area of our API is extremely stable and it shouldn't be too much overhead to keep some manually generated pages in sync, as well as this allowing for more human curating of the content with some commentary and grouping of related APIs etc.
Anastasia Cheetham September 18, 2014 at 7:30 PM
Apparently, Steve has updated the source code for infusion-tags. We should revisit the tool and make a final decision on whether or not to use it.
Generate documentation for the Infusion Framework API functions from the source code using infusion-tags. And integrate the output into the DocPad HTML docs generation.