If we know we want a Tour de FlexJS, one plan would be to create a Git repo for it and recruit volunteers to start migrating Tour de Flex to this new repo. Then we'd learn what to put in our migration document as well.
Thoughts? -Alex On 9/9/16, 2:49 AM, "OK" <p...@olafkrueger.net> wrote: >Christofer Dutz wrote >> You can also have a look at the output it creates at [1] > >Looks very promising to me! > >What would be the steps to achive a FlexJS component documentation using >this technique? >Probably we have to place one of these Asciidoc files for each relevant >strand and bead? >Would the component docs be part of the existing site build or inside its >own shell. >Would it be possible to include ASdocs with some magic? > >Only to consider another option: >I just realize that the flex asdoc [1] are part of Apache. >Are there also tools available to build this also nice documentation? > >Olaf > >[1] https://flex.apache.org/asdoc/ > >Olaf > > > >-- >View this message in context: >http://apache-flex-development.2333347.n4.nabble.com/FlexJS-Starting-with- >the-Docs-tp55005p55016.html >Sent from the Apache Flex Development mailing list archive at Nabble.com.
