What kind of documentation are you talking about? Just filling out ASDoc, or pages of words?
There are so many things that need to be done that having folks who aren't currently committing code to FlexJS help with filling out ASDoc and recruiting people who are good at writing to write more verbose documentation would be a great help. I don't agree that doc is more important than functionality until you have enough functionality, and the lack of a testimonial makes me think we aren't quite there yet. If someone tried FlexJS and isn't sure what they can do, a more specific question/comment would help. We could create a JIRA issue called "FlexJS Doc Wish list" and folks can comment in there. We can't guess what folks need. It would be better for folks to try to do what they want to do and if it can't do it, they should ask about it. Thanks, -Alex On 9/8/16, 12:18 AM, "Harbs" <harbs.li...@gmail.com> wrote: >+1000 > >Documentation is the first thing people look for in a framework. This is >absolutely critical (more than functionality and production apps). >Unfortunately, I’m really bad at documentation, so I can’t help much with >this. > >AFA productions apps go, my conversion to FlexJS is moving along quite >nicely. I don’t have an ETA yet, but I’m really hoping it will be usable >by the end of the year (and hopefully sooner). > >On Sep 8, 2016, at 9:27 AM, piotrz <piotrzarzyck...@gmail.com> wrote: > >> In my opinion documentation is the second thing which need to be done >>before >> 1.0 >
