Hi Nicolas,
2017-10-22 23:34 GMT+02:00 Idylog - Nicolas Granon <[email protected]>:
> Hi Carlos,
>
> Amazing work !
>
>
Thanks! Glad you like it :)
> 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").
>
>
Yes! I think it's as well very "Apache" since oranges and blues and whites
are very near of what Apache id in some cases, but with some extra energy
and vitality IMHO that makes it to have a positive punch ;)
> 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...
>
>
the problem with logo is that I even think in simplified it more since in
the end made me have some problems to insert it in tiny spaces, so I prefer
to simplify instead of insert more things... I even think about other logo,
maybe I could try it another one I have in mind, although don't not if have
the time, and maybe better to continue to get the final 1.0 and maybe later
revisit that.
> 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".
>
For me docs should have that: Links to a main tutorial (Getting Started),
wiki, reference, video tutorials, etc...
Is the main point of entry for people that wants to learn Royale.
>
> 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.
>
I expressed in other threads that we should avoid "Flex" word and
references as much as we can. We want to have a new opportunity and other
people has express me "how much we need a change of name, look and
more...". This days Flex word is "cursed" on IT or at least is my
experience. So maybe Flex references could be done is something more
separated from us, maybe in other web, blog, etc...
In the other hand, people that nows Flash, Flex, AIR etc... we'll know us
and if they want to use Royale to migrate we'll do without the need to read
in our site nothing about Flex.
That's my opinion and thought in what I think we should do in marketing
terms if we want to compete with angular, react, and the rest
>
> 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).
>
Yes, we can do it as we want, the content here is still to be defined and
done. I think we need more "blocks" covering the great things we can do
"Maven, AMF, ....
>
> 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.
>
Right! Without doubt! thanks! :)
(don't think we have any problem with FP legal)
>
> Maybe the term "framework" should be used ?
>
>
I prefer "technology" over "framework", since is a compiler, 2 languages,
and a framework, but we can see what others think about it, maybe more an
SDK, although does not like that word too much since others like Angular or
React are more simple, and we need to expose the thinking of great ease of
development, and maybe and SDK sounds more complicated...mmm...is a
question of "feelings" here for me.
> 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...
>
Yes, is an effect given by the theme, we can remove them or make It more
noticeable. works when moves the mouse over the page.
>
> 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").
>
Right, is what the apache rules said, so we must do as it. in the other
hand is normal since internet has many, many info nowadays for almost
anything you can search ! :)
> 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).
>
great! I think we should add an Stackoverflow link as we have some content
there as well ;)
> The whole community should always use "Apache Royale" and never use
> "Royale" alone.
>
> My 0.02 euro !
>
Many thanks Nicolas! :)
>
> 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
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
