why such the short list? ;) On Wed, Apr 4, 2012 at 12:15 PM, Omar Gonzalez <omarg.develo...@gmail.com> wrote: > Can't think of a reason why that wouldn't be a good idea, go for it I say! > :) > > -omar > > On Wednesday, April 4, 2012, Keith Sutton wrote: > >> In the spirit of 'just do it' here is a pretty comprehensive list of Flex >> ecosystem partners and their products/services: http://www.spoon.as/flex-* >> *ecosystem-products/ <http://www.spoon.as/flex-ecosystem-products/> >> >> This was not a trivial tasks because digging for and connecting with the >> Product Managers of these organizations and getting >> descriptions/links/icons ironed out took time. Clearly some design finesse >> is needed. >> >> I was envisioning summarizing this list on an Apache Flex page similar to >> http://wiki.apache.org/hadoop/**HadoopUserGroups<http://wiki.apache.org/hadoop/HadoopUserGroups> >> >> Happy to work on this page on Apache Flex wiki while the discussion on a >> web site goes on. At least the data will be there. >> >> Any disagreements? >> >> >> >> On 4/4/2012 5:49 AM, Ivan Ilijašić wrote: >> >>> On Wed, Apr 4, 2012 at 2:46 PM, Martin Heidegger<m...@leichtgewicht.at >>> >wrote: >>> >>> Imho the order is not right. The structure of a page is crutial for >>>> starting the design process. So how about collecting things that need to >>>> be >>>> shown on the Flex homepage, here is what I can think of: >>>> >>>> - Download the SDK >>>> - Documentation to the SDK (big topic) >>>> - Team (&how to join) >>>> - Examples >>>> - Twitter/Google+/Mailinglist/****etc. (socializing) >>>> - Source access (svn/github mirror/etc.) >>>> - License >>>> - FAQ >>>> - Coding Standards >>>> >>>> I agree with Martin. Also I would suggest adding showcase subpage. >>> >>> Cheers, >>> Ivan >>> >>> >>
-- JP Bader Principal Zavteq, Inc. @lordB8r | j...@zavteq.com 608.692.2468
