-
Notifications
You must be signed in to change notification settings - Fork 36
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
Kata order not apparent, but it is important #10
Comments
the idea is great and in here Kind regards / Saludos / Mit freundlichen Grüßen [email protected], mobile: +49 174 300 4595 ECMAScript6+React.js workshop http://meetu.ps/2Jds4D uxebu GmbH Amtsgericht Augsburg, Handelsregister HRB 28613 On Mon, Jun 29, 2015 at 3:50 AM, Shawn Erquhart [email protected]
|
Okay, cool. Is the design from issue #1 something you would like to see implemented as well? The current look does have this cool, raw feel to it - I'd likely alter the design a bit so as not to lose that. |
Tbh I took inspiration from #1 but that's it.
|
So you're saying you like the design as is, correct? |
Mmmh, I don't really. I would be open to more modern looks
|
Esp enabling some things like more info about each kata group or maybe even
|
Makes sense. Can you get a hold of the psd from #1? Could be used as a base. |
Not sure if #1 works when the number of katas grows ...
|
I actually think it will work just as well as the current setup - the section containing the katas will simply grow to house them and the page will scroll. We could also make the structuring more similar to the current one by using a block grid instead of the two column list in the design. At a glance I would reduce the size of the illustration and potentially name the sections. Prerequisites for individual katas could be revealed by expanding on hover. @MadameLeRenoir, was there a psd for your design? |
Sure got a Pixelmator file which you can import. I thought the issue for a redesign was already closed? Sent from my iPhone
|
@tddbin (Wolfram I believe?) is open to it, see comment string above. |
Let the inspiration flow ...
|
@MadameLeRenoir Pixelmator file would work great :) |
that shows all the stuff we need. i like the idea! Kind regards / Saludos / Mit freundlichen Grüßen [email protected], mobile: +49 174 300 4595 ECMAScript6+React.js workshop http://meetu.ps/2Jds4D uxebu GmbH Amtsgericht Augsburg, Handelsregister HRB 28613 On Tue, Jun 30, 2015 at 10:59 AM, Julian Hollmann [email protected]
|
Would be awesome if someone comes up with a design based on this layout. |
Awesome concept. Considering the utilitarian nature of the project, I'd say this is pretty close already. Just add color, typography and branding. The real work will be tracking things (could use local storage, just easy to lose your data), gathering documentation links, and creating examples. This also shifts the site from static single page to single page app. |
I am back to this idea too, because I somehow feel I want to strengthen the learning aspect of the katas and try to lead people a bit more, if there is still interest I would be curious to implement some cool design. Please come forward. I just can't design at all :) |
I haven't completed the Array API kata yet, but It's already assumed knowledge of a few es6 concepts covered in other katas. Since the katas are my first dive into es6, I had to go learn those things to complete the work.
Have you considered setting an obvious order for these, so that learning is progressive? As I said, I'm working on the Array API kata, but I'm not sure if it's at the top left because it's oldest or newest - there's no clear starting point. Running into concepts covered in other katas makes me feel like I'm going out of order.
The design offered in #1 avoids both of these issues - if it was not accepted for time constraints, I may be able to help get it implemented. Let me know.
Also, in case this is unintentional, this is how the layout looks for me (Chrome stable, Win 8.1):
The text was updated successfully, but these errors were encountered: