Wow - really like this! Very clean and elegant.
I think we should /show/ a little bit more what we mean by
modeling/deploying/managing -- eg for modelling (code snippet), and a
graphic w cloud icons for deploy, and maybe a UI screenshot for manage ?
And not sure about curl-to-bash for install -- some people are
uncomfortable with that (in any case we should curl from an apache site
for a release, not github). But some one-line quick start would be
nice. A docker image? (And can say jump to Get Started for other
flavours of installs.)
Lastly instead of the brooklyn logo font, can you just use the big logo
PNG that is currently in use on the site?
Best
Alex
On 17/04/2017 21:50, Thomas Bouron wrote:
HI Alex, all.
I have played a bit over the week end with a prototype and here is what I
came up with for the homepage[1].
I reworded a bit to be more clear and simple but that obviously can change.
I also updated the feather to use the new one.
What do you think?
PS: I don't have the right font for Apache Brooklyn. Does anyone know which
one is it?
Best.
https://drive.google.com/file/d/0BxboJOOp7N8CVkppSE1QaEhkSGc/view?usp=sharing
On Thu, 13 Apr 2017 at 17:08 Thomas Bouron <[email protected]>
wrote:
Hi all.
Massive +1 Alex. I also think we can hugely improve the website from a
UI/UX perspective. Valentin also raises a good point about the SEO which is
far from being optimised.
I would happily help on that.
Best.
On Thu, 13 Apr 2017 at 15:32 Alex Heneveld <
[email protected]> wrote:
Hi folks-
I've been hearing two categories of feedback from people who've spent
time on our website: "I don't get it" and "Sounds complicated".
I think the time is right for us to fix this. We can give a clear,
gentle experience, and we can tone down the academic ideas in favour of
real examples, which thanks to recent improvements are pretty simple.
I'm thinking of a few changes:
* Expand and ground the landing page (currently it's all academic theory
words words words) -- I attach a mock-up of how this could look in the
attached (based on other sites)
* Rework the Getting Started example to be something using bash, rather
than a magic java entity
* Instead of YAML/Java blueprints, call it "Basic Blueprints" "Advanced
Blueprinting", make the "Basic Blueprints" section nice simpler
reference pages, with much of the content moved into advanced (where the
Java items might get buried further)
What do other people think? Should we have a chat? Say next Fri 4pm UK ?
Best
Alex
--
Thomas Bouron • Senior Software Engineer @ Cloudsoft Corporation •
https://cloudsoft.io/
Github: https://github.com/tbouron
Twitter: https://twitter.com/eltibouron
