Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New website look and feel - design brief #9709

Open
johnspackman opened this issue Jun 24, 2019 · 14 comments

Comments

Projects
None yet
6 participants
@johnspackman
Copy link
Member

commented Jun 24, 2019

With the impending 6.x release, we would like to create a new website with a fresh look and feel - we're going to outsource the work to a professional designer on a paid basis, and so we need to create a design brief for him to work from.

This issue is to help us form that design brief, and we welcome opinions and thoughts from everybody, not just core team members.

The goal at the end of this issue is to have a design which is primarily used for the public website, and serves as promotional brochure website as well as hosting documentation, API viewer, demo apps, etc.

We have some design work already done a while ago (generously donated by @cajus) and while it's been successfully used in the implementation of qx serve, further work has stalled. The design could form a basis for the new designs, or it might not - the important take away is that opinions are wanted and nothing is set in stone. Here's a screenshot of this design

Screenshot 2019-06-24 at 11 30 26

@johnspackman

This comment has been minimized.

Copy link
Member Author

commented Jun 24, 2019

Personally, I quite like the design above - it hits a lot of my boxes for new modern look; the logo is OK, and is quite clever in how (once you know that is's for Qooxdoo) it ties in with the name.

IMHO what's missing is a style guide for content generally and a design for the home page.

For example, would we want a long home page? IMHO long pages require sub navigation so you can see where you are, but this can be designed in nicely and then there's those sexy parralax-type effects.

The real question for the home page is not so much the design, but what do we want on it?

Here's some ideas off the top of my head:

  • Build rich, Single Page Applications using OO development, No CSS or HTML required
  • Wide range of UI components
  • Powerful Server I/O communication
  • Cross platform, built in ES6-everywhere (including server and mobile)
  • 100% Javascript including tooling and user interface testing
  • Over 10 years of development
@oetiker

This comment has been minimized.

Copy link
Member

commented Jun 24, 2019

I have been working with flutter.dev (for writing a native mobile app) over the last week and they have a pretty simlilar 'narrative' to ours they also say you should be able to write your application in a single language ... without css/xml/dom ... pretty interesting to read their stuff :) flutter could often be replaced by qooxdoo directly ...

@johnspackman

This comment has been minimized.

Copy link
Member Author

commented Jun 24, 2019

Looking at the flutter.dev website, it is a nice clean look and reminds me of the google material theme.

And thinking about design, it would be very nice if the new website should echo the design ethos of the new UI appearance - which AFAICR we wanted to base on @oetiker 's material theme https://github.com/oetiker/qx-osparc-theme (is this still the plan?)

@johnspackman

This comment has been minimized.

Copy link
Member Author

commented Jun 24, 2019

What I love about Qooxdoo is that it brought desktop development to the browser - after a decade as a C++ and Java developer, being dropped into native javascript was like having a lobotomy. OO class design is a really strong feature, and on the odd occasion that I've looked at other "OO" class libraries they just don't compare.

So I guess that one feature I'd like to see promoted is that it is a high quality engineering tool of classes and libraries - and at the other extreme it's easy to get to grips with and well documented.

@cboulanger

This comment has been minimized.

Copy link
Contributor

commented Jun 24, 2019

Also, the wealth of tools such as the playground, demobrowser, apiviewer etc. that we inherited is a real asset. And the fact that even if most of the codebase is 10 years old, hardly anything needs an update except when browsers change in backward-incompatible ways.

@yybalam

This comment has been minimized.

Copy link

commented Jun 24, 2019

Hi. By the moment I just have comment about the new logo design, I love that «Q», however IMHO a kind of «</>» could reflect better the code nature than an «X». Of course, I'm guessing that pro designer will to propose some changes, but well, I'm just saying. :)

@voger

This comment has been minimized.

Copy link
Contributor

commented Jun 24, 2019

Maybe mention somehow that developing with Qooxdoo looks more like Class inheritance vs Prototypal. We have Interfaces, Abstract Classes, Mixins.

@johnspackman

This comment has been minimized.

Copy link
Member Author

commented Jun 25, 2019

I've started summarising the brief here:

https://github.com/qooxdoo/qooxdoo/wiki/New-Website-Brief

@cboulanger

This comment has been minimized.

Copy link
Contributor

commented Jun 25, 2019

Maybe we can advertise it as the "hidden gem" - since it is almost never in the javascript news, but has been powering desktop-grade applications for over 10 years. We should also add a section on history in the docs that explains the origins as an inhouse-project at 1&1 and its transformation into a foundation, with important milestones. It helps that the demos of all releases are still there and still work !!!

@johnspackman

This comment has been minimized.

Copy link
Member Author

commented Jun 26, 2019

Also, in no particular order:

  • Advanced property mechanism with binding and forms.
  • Baked in support for Promises
  • Webfonts
  • Package manager
  • Annotations
  • Automatic Memory Management
@hkollmann

This comment has been minimized.

Copy link
Member

commented Jun 27, 2019

On the old website we had a section real life examples. Could we get that back on the new page?

@cboulanger

This comment has been minimized.

Copy link
Contributor

commented Jun 27, 2019

@hkollmann This could be made part of the docs (easier to update) and then the website links to it. Maybe docs/reallifeexamples.md?

@johnspackman

This comment has been minimized.

Copy link
Member Author

commented Jul 9, 2019

Recent discussion about styling:

@cboulanger said
The designs of the competition is very uniform: https://reactjs.org/ https://dojo.io/ https://dojotoolkit.org/ https://vuejs.org/ https://angular.io/ https://www.meteor.com/
Ember and Polymer stand out: https://emberjs.com/ https://www.polymer-project.org/
Maybe we could have something out of the ordinary?

@oetiker said
I would not go too far out, as people should associate us with the general topic, so blending in to some degree is not all bad :)

@johnspackman said
ok; how do we feel about the logo?

@cboulanger said
I like the logo. I associate Qooxdoo with architecture and good engineering, maybe he could use some of this imagery as inspiration?

@cboulanger said
Nuts and bolts, construction site, scaffolding etc.
Please no cute mascot!

@cboulanger

This comment has been minimized.

Copy link
Contributor

commented Jul 10, 2019

Maybe some imagery in this direction? https://ya-webdesign.com/explore/svg-gear-machine/
The "Gear" imagery is already present in the current logo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.