Update homepage to use different theme
Update homepage to use a different theme.
The documentation css heavily borrowed from another open source project. Apparently the other author intended for the css library code to be open source, but didn't want people to use the css theme, which is reasonable - so we should change it.
Original source was: https://github.com/philipwalton/polyfill/tree/gh-pages
Which had the following license document:
(The MIT License) Copyright (c) 2013 Philip Walton <http://philipwalton.com> Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
I have requested a friend of mine to come up with some mockups (using existing open-source themes).
We might need to find a designer to help. My main dislikes are:
- The content above the fold is useless in helping the user understand what the library is about. This is already bad enough with the existing page. I would actually take the big brown box from the original page (https://www.javapoly.com/) and shrink it down to just be the size of the sticky header on your mockup. When people visit the page, the first thing they should see should be the introduction / high-level description.
- The mockup has a sticky header that is about the right size, but probably shouldn't be sticky.
- I don't really like the new colors. I really liked the browns and tans because Java is a type of coffee, and the coffee bean colors felt right for a Java project :P. That's actually the main reason I selected the above open source theme.
After digging deeper into the license details and talking with the author, I think he did intend for the theme to be open source, but wanted users of the theme to adapt the page sufficiently that it wouldn't be confused with the original site. Because the content above the fold looked almost identical on the two sites, I think that is why the original author had such a negative gut reaction. He might be ok with it if we sufficiently modify the theme. I think we should try making some changes, and then I'll ping him again and get him to sign off on the new theme as acceptable (try to keep everyone happy).
I've attached a draft of a new header that I think is better for this project anyway. It is inspired by the header in the freelancer theme you linked.
I agree with your comments and I like the mockup you attached!
We have three options:
- Take the current CSS as base and modify it to suit the new mockup. Add responsiveness if desired.
- Start with the
freelancertheme as base and alter it to match the new mockup. Remove the "hero" element, make the header non-sticky, change the color, etc.
- Wait for a designer (which me and my friend are not) to do it right.
Let me know which option to go with.
Let's go with the first option for now, and see where that takes us. We can find a designer if more aggressive changes are needed, but that takes time.
To make this banner, I actually just took the banner from the
freelancertemplate, and changed the background color to match the current brown. The "Java(Script) in the browser" text is the same font/size as the links on the right side of the banner. Should be fairly straight forward.
We should probably also do some work to make the demo a little sexier. At the very least, make it clear when the demo is still loading and give some sort of progress bar like John's demo has.