Ideas to improve the homepage

[davelab6]

• [ ] Make a link to https://github.com/byte-foundry/pluminjs-website/ and https://github.com/byte-foundry/plumin.js/ - prominently
• [ ] Make a link to https://github.com/byte-foundry/pluminjs-website/issues/new and https://github.com/byte-foundry/plumin.js/issues/new - prominently
• [ ] Make the examples contentEditable and emphasise that these examples are real text with real fonts.

You might need to do something to restrict the chars that can be input, and give a feedback to the user when they try to key a char which isn't supported... but I think that even without that, the demos do not really convey the power of what plumin is doing. I think otherwise its possible the audience may not 'get it' and say,

well, its using paperjs to draw via a font, but whatevs, plain paperjs with canvas (or plain canvas or svg) is fine, I don't see the point of this

• [ ] The top nav bar scrollspy is broken in mac Firefox, I expect you know
• [x] the first demo with a p is broken in mac Firefox, I expect you know
• [ ] In the mobile version, its a bit tricky to scroll when the twitter and commit iframes take up almost all the screen, so maybe make them a bit more narrow so there is a bit more right margin to grab and use to scroll with
• [ ] In the mobile version, the interpolate is line wrapped as below, so resize it to be on 1 line:

Hamburg er

• [ ] The slider widget sucks for touch input, use something better for mobile
• [x] Put a redirect on http://byte-foundry.github.io/plumin.js/# to this new site
• [ ]

[louisremi]

Thank you for the detailed feedback. We won't have the time to tackle all these issues right now but I hope we'll be able to get an intern to do additional work on this page in March. The mobile version deserves some love, for sure.

I've reworked the first demo as well as the wording of the first paragraph to better explain the explanation of the purpose of Plumin.js