Hi Carlos,
Amazing work !
Some comments / opinions :
Color scheme :
I believe the chosen contrasting colors are an excellent choice. It is very
distinctive and very "branding" (I'm not talking about my personal taste, but
about visual perception) .
I suggest that this color scheme could be the "default theme" for Apache Royale
apps (it needs some enhancements like "hovered", "selected"... but the base
seems quite promising).
A good "default theme" is important for all of us who build enterprise
applications where the theme is not a primary concern. We need something with
strong visual ergonomics, not too fancy... something a CFO will find "modern"
and "serious").
Logo
Quite appropriate and also quite distinctive.
I'm wondering if the "lines crossing points" should be a small circle too...???
The "bridge" does not quite fit the "jewel" concept...
Site organization
Maybe there could be two distinct entries : "tutorials" and " docs" (in your
sample, "docs" leads to "browse and learn"). Or maybe "docs" should be
"tutorials and docs".
Maybe there should be an explicit entry "from flex to apache royale" since we
expect many people will come to Apache Royale while searching for a migration
path.
That entry should lead to "migration related" docs. I believe many people
coming from Flex are interested in a global overview of the migration process
and that deserves a dedicated entry.
Maybe the "features" page should mention AS3, MXML, Javascript ? (that would
help people searching with those keywords) (I saw that these are mentioned on
the home page, but maybe it's worth mentioning it again on the features page).
Maybe the "features" page - or even the home page - should mention that Apache
Royale allows developing applications in AS3/MXML *without the need for Flash
Player* ? (that is certainly something many people are looking for !!!).
Furthermore, maybe the features page should explicitly talk about "Flex
replacement" ?
Maybe this raises legal issues ? But if it is possible, I believe this should
be mentioned in at least one place because it would get a lot of "hits" from
search engines.
FP end of life is certainly an issue for many people.
Maybe the term "framework" should be used ?
Something weird :
On my browser (Firefox), on the features page, the "Enterprise class
programming model" block (the title + the text) seems to move slightly before
"finding its final location"...???
This appears each time the mouse hovers that block...
Side note :
The choice of "Royale" as a framework name is not bad I itself.
However, it produces *lots* of noise when searching with google.
I suggest that "royale" should **never** be used alone (web site, docs,
tutorials, blogs, wiki...) but **always** associated with Apache ("Apache
Royale").
That would make google searches much more efficient and usable (provided the
users know that Royale is an Apache project !!!).
This should also be enforced on 3rd party sites (like StackOverflow).
The whole community should always use "Apache Royale" and never use "Royale"
alone.
My 0.02 euro !
Regards,
Nicolas Granon
> -----Message d'origine-----
> De : [email protected] [mailto:[email protected]] De la
> part de Carlos Rovira
> Envoyé : dimanche 22 octobre 2017 20:29
> À : [email protected]
> Objet : Apache Royale WebSite Preview
>
> Hi All,
>
> here's the propose I've been working this past weeks for the Apache
> Royale website.
>
> Disclaimer: Have in mind that is only a propose, not the final site, so
> there's more work to do, but first I want to expose the work in
> progress and discuss some things about it.
>
> http://royale.codeoscopic.com
>
> (still is the subdomain I've been working on in the final site)
>
> The pages I use to define a style and the ones you can look at:
>
> Home - http://royale.codeoscopic.com/
> Features - http://royale.codeoscopic.com/features/
> Mailing List - http://royale.codeoscopic.com/mailing-lists/
>
> (again disclaimer: no one is still finished, I put some pieces in play,
> but that could not be final at all, or it could be maybe with some
> changes)
>
> I worked mainly in:
>
> * Menu Organization: That's crucial for a good web site. Look that
> there's no submenus. All is directly accesible in all pages of the
> site.
> Main things are in the header main menu (what we want to focus) Rest
> are in the footer. I worked specially in this part to get a good
> looking but simple menu that will be present though all web site.
>
> * Colors (orange-blue)
> * Fonts
> * Logo definition (to get clean)
> * Apache guidelines (copyrights, links to apache, license....)
>
> To make this I studied :
>
> * Other Apache websites (to see how they did it: Flex, Struts, and so
> on...)
> * Competence websites (how others are doing it mainly in the frameworks
> most popular today: Angular, React,...)
>
> As well and of course other well designed and modern websites out
> there.
>
> Think that I did as well some blender 3d rendering art, but I plan to
> do more in the next phase as we discuss content.
>
> Please, take a look at it and let me know what you think.
>
> We can open other thread to discuss about content.
>
> Hope you like it! :)
>
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
