Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 7.0.0
    • Component/s: site
    • Labels:
      None

      Description

      Our current site design has been with us for quite a while. It looked fresh in the 1980s, but now it has gone stale.

      This is a proposal for a new, fresh design of the home page and sub pages.

      The home page will feature a prominent download link, a list of feature descriptions, screenshots of sites powered by Wicket, official blog items and Buzz by our users.

      The screenshots of wicket powered websites will link to short descriptions of the sites under /meet/poweredby. Links to the websites will of course have nofollow

      Other pages will feature a menu on the right side of the page providing direct links to content.

      Attached are a couple of screen shots of how the site might look like.

      Screen 005 is an alternative of the home page without the list of features, but including the introduction to wicket article.

      1. wicket-site-new.018.png
        500 kB
        Martijn Dashorst
      2. wicket-site-new.017.png
        470 kB
        Martijn Dashorst
      3. wicket-site-new.016.png
        412 kB
        Martijn Dashorst
      4. wicket-site-new.015.png
        385 kB
        Martijn Dashorst
      5. wicket-site-new.014.png
        494 kB
        Martijn Dashorst
      6. wicket-site-new.013.png
        433 kB
        Martijn Dashorst
      7. wicket-site-new.012.png
        366 kB
        Martijn Dashorst
      8. wicket-site-new.011.png
        430 kB
        Martijn Dashorst
      9. wicket-site-new.010.png
        475 kB
        Martijn Dashorst
      10. wicket-site-new.009.png
        362 kB
        Martijn Dashorst
      11. wicket-site-new.008.png
        384 kB
        Martijn Dashorst
      12. wicket-site-new.006.png
        680 kB
        Martijn Dashorst
      13. wicket-site-new.005.png
        567 kB
        Martijn Dashorst
      14. wicket-site-new.004.png
        510 kB
        Martijn Dashorst
      15. wicket-site-new.003.png
        497 kB
        Martijn Dashorst
      16. wicket-site-new.002.png
        466 kB
        Martijn Dashorst
      17. wicket-site-new.001.png
        423 kB
        Martijn Dashorst
      18. logo.wicket.ai
        1.06 MB
        chrisjlee
      19. logo.wicket.jpg
        10 kB
        chrisjlee
      20. Keynote001.png
        232 kB
        Martijn Dashorst
      21. wicket-logo-big.png
        43 kB
        Michael Mosmann
      22. wicket-logo.svg
        62 kB
        Michael Mosmann
      23. wicket-flat-new-top.005.png
        213 kB
        Martijn Dashorst
      24. wicket-flat-new-top.004.png
        208 kB
        Martijn Dashorst
      25. wicket-flat-new-top.003.png
        224 kB
        Martijn Dashorst
      26. wicket-flat-new-top.002.png
        240 kB
        Martijn Dashorst
      27. wicket-flat.001.png
        245 kB
        Martijn Dashorst
      28. ASF.LICENSE.NOT.GRANTED--Alternative design.jpg
        283 kB
        Martijn Dashorst
      29. KeynoteScreenSnapz005.png
        326 kB
        Martijn Dashorst
      30. KeynoteScreenSnapz004.png
        187 kB
        Martijn Dashorst
      31. KeynoteScreenSnapz003.png
        183 kB
        Martijn Dashorst
      32. KeynoteScreenSnapz002.png
        128 kB
        Martijn Dashorst
      33. KeynoteScreenSnapz001.png
        327 kB
        Martijn Dashorst

        Issue Links

          Activity

          Hide
          Igor Vaynberg added a comment -

          looks awesome. my vote is for 001. i think 005 leaves too little space for news. also more pictographs would help. like an icon for each feature. right now seems a little too much text.

          another idea may be to make features a timed slider where its a feature followed by a small code snippet. maybe.

          Show
          Igor Vaynberg added a comment - looks awesome. my vote is for 001. i think 005 leaves too little space for news. also more pictographs would help. like an icon for each feature. right now seems a little too much text. another idea may be to make features a timed slider where its a feature followed by a small code snippet. maybe.
          Hide
          Andrea Del Bene added a comment -

          +1 for 001

          It's VERY nice and despite the big amount of information it gives it's very clear.

          Show
          Andrea Del Bene added a comment - +1 for 001 It's VERY nice and despite the big amount of information it gives it's very clear.
          Hide
          Martijn Dashorst added a comment -

          Alternative, less cluttered design

          Show
          Martijn Dashorst added a comment - Alternative, less cluttered design
          Hide
          Chris Colman added a comment -

          Looks great! Go live already!

          Show
          Chris Colman added a comment - Looks great! Go live already!
          Hide
          Bruno Borges added a comment -

          The alternative design looks awesome. +1 for that

          Show
          Bruno Borges added a comment - The alternative design looks awesome. +1 for that
          Hide
          procrastinative added a comment -

          hello Martin, can you upload a psd's. I will help you with creating a new version of wicket site.

          Show
          procrastinative added a comment - hello Martin, can you upload a psd's. I will help you with creating a new version of wicket site.
          Hide
          Martin Grigorov added a comment -

          The new website is at https://github.com/dashorst/wicket-site.
          I don't see .psd files there but I hope it is enough for you to help us!

          Show
          Martin Grigorov added a comment - The new website is at https://github.com/dashorst/wicket-site . I don't see .psd files there but I hope it is enough for you to help us!
          Hide
          procrastinative added a comment -

          Which version of design is currently full approved?

          KeynoteScreenSnapz001.png to KeynoteScreenSnapz005.png have consistent look, but I agree with other people that Alternative_design.jpg looks better.

          So, for index.html I should use alternative_design and for the rest use KeynoteScreen1-4 or use KeynoteScreen1-5 for all?

          Show
          procrastinative added a comment - Which version of design is currently full approved? KeynoteScreenSnapz001.png to KeynoteScreenSnapz005.png have consistent look, but I agree with other people that Alternative_design.jpg looks better. So, for index.html I should use alternative_design and for the rest use KeynoteScreen1-4 or use KeynoteScreen1-5 for all?
          Hide
          Martijn Dashorst added a comment -

          What I'm aiming at is something that requires the least amount of maintenance. That's why I'd like to utilize bootstrap. But is is also why I don't like to have the website screenshots directly in the page (would be hard to maintain).

          The alternative is a bit cumbersome to craft. Perhaps we should take a step back and see how we want the site to be structured rather than jump of a bridge and go do something.

          Show
          Martijn Dashorst added a comment - What I'm aiming at is something that requires the least amount of maintenance. That's why I'd like to utilize bootstrap. But is is also why I don't like to have the website screenshots directly in the page (would be hard to maintain). The alternative is a bit cumbersome to craft. Perhaps we should take a step back and see how we want the site to be structured rather than jump of a bridge and go do something.
          Hide
          procrastinative added a comment -

          I can offer cutting and html creation, i don't have any design skills, so someone should prepare jpg/psd mock etc and after that I will do rest of the job.

          Bootstrap is good idea, but is not to sterile? In my opinion alternative_design is good because doesn't look like 'common' template. I think we should create main pages for wicket site using sth like alternative_desing template and from it link to other resources that looks based on for example bootstrap.

          We can minimalize our effor to maintain wicket site by using cms (sth written in php or brickx - jvm hosting is a problem?). How much effort jekyll needs?

          Show
          procrastinative added a comment - I can offer cutting and html creation, i don't have any design skills, so someone should prepare jpg/psd mock etc and after that I will do rest of the job. Bootstrap is good idea, but is not to sterile? In my opinion alternative_design is good because doesn't look like 'common' template. I think we should create main pages for wicket site using sth like alternative_desing template and from it link to other resources that looks based on for example bootstrap. We can minimalize our effor to maintain wicket site by using cms (sth written in php or brickx - jvm hosting is a problem?). How much effort jekyll needs?
          Hide
          Martijn Dashorst added a comment -

          A flat, more contemporary graphics design

          Show
          Martijn Dashorst added a comment - A flat, more contemporary graphics design
          Hide
          Andrea Del Bene added a comment -

          VERY nice! Bravo!

          Show
          Andrea Del Bene added a comment - VERY nice! Bravo!
          Hide
          Martin Grigorov added a comment -

          I like the new one too!

          Show
          Martin Grigorov added a comment - I like the new one too!
          Hide
          Martijn Dashorst added a comment - - edited

          Animation of front page when scrolling up reveals the top menu bar with logo. see wicket-flat-new-top-*.png

          Show
          Martijn Dashorst added a comment - - edited Animation of front page when scrolling up reveals the top menu bar with logo. see wicket-flat-new-top-*.png
          Hide
          Michael Mosmann added a comment -

          IMHO the "w" in the wicket logo is too small.. i did as best as i could a reverse engineered version of the original logo.

          Here is the inkscape-source-file (and a exported version as png). This way it should be easy to make it "flat"..

          Show
          Michael Mosmann added a comment - IMHO the "w" in the wicket logo is too small.. i did as best as i could a reverse engineered version of the original logo. Here is the inkscape-source-file (and a exported version as png). This way it should be easy to make it "flat"..
          Hide
          Martijn Dashorst added a comment -

          small screen site layout example

          Show
          Martijn Dashorst added a comment - small screen site layout example
          Hide
          Martin Grigorov added a comment -

          Every time I read/hear "mobile first" and I remember of http://s3-ec.buzzfed.com/static/enhanced/webdr02/2013/7/25/11/enhanced-buzz-6550-1374767315-12.jpg

          "small screen site layout example" looks very nice!

          Show
          Martin Grigorov added a comment - Every time I read/hear "mobile first" and I remember of http://s3-ec.buzzfed.com/static/enhanced/webdr02/2013/7/25/11/enhanced-buzz-6550-1374767315-12.jpg "small screen site layout example" looks very nice!
          Hide
          chrisjlee added a comment - - edited

          This issue still under progress? I'd love to contribute. I'm a new contributor (haven't contributed yet) and would like to work on this.

          I think we should keep this hosted on github pages to allow for anyone to edit.

          Show
          chrisjlee added a comment - - edited This issue still under progress? I'd love to contribute. I'm a new contributor (haven't contributed yet) and would like to work on this. I think we should keep this hosted on github pages to allow for anyone to edit.
          Hide
          Martin Grigorov added a comment -

          Hi chrisjlee,

          Please take a look at https://github.com/dashorst/wicket-site/tree/responsive (note: branch "responsive").
          Any help here is very welcome!
          You can also give us a hand with WICKET-3435.

          Show
          Martin Grigorov added a comment - Hi chrisjlee , Please take a look at https://github.com/dashorst/wicket-site/tree/responsive (note: branch "responsive"). Any help here is very welcome! You can also give us a hand with WICKET-3435 .
          Hide
          chrisjlee added a comment - - edited

          Great thank you. I've forked and cloned project and the site looks close. Needs some mobile fixing up. Will keep everyone updated.

          My fork is located here: https://github.com/chrisjlee/wicket-site

          Show
          chrisjlee added a comment - - edited Great thank you. I've forked and cloned project and the site looks close. Needs some mobile fixing up. Will keep everyone updated. My fork is located here: https://github.com/chrisjlee/wicket-site
          Hide
          chrisjlee added a comment - - edited

          Martin Grigorov
          Would it be possible to adjust the wicket logo to match the new flat look of the website ? I'd like to remove the internal dropshadow and give it more contemporary fresh look.

          Show
          chrisjlee added a comment - - edited Martin Grigorov Would it be possible to adjust the wicket logo to match the new flat look of the website ? I'd like to remove the internal dropshadow and give it more contemporary fresh look.
          Hide
          Martin Grigorov added a comment -

          Everything is possible ! Go ahead!
          You can write to dev@wicket.apache.org mailing list and ask for opinions which logo to use if you have several ...

          Show
          Martin Grigorov added a comment - Everything is possible ! Go ahead! You can write to dev@wicket.apache.org mailing list and ask for opinions which logo to use if you have several ...
          Hide
          chrisjlee added a comment -

          AI file for the logo

          Show
          chrisjlee added a comment - AI file for the logo
          Hide
          Chris Colman added a comment - - edited

          I'm hoping that this JIRA could be completed soon after recent emails in the mailing list. I have added some subtasks to capture some things that probably need doing, marking anything that prevents 'go live' with "Blocker" priority and all others that should not stop the go live as any other priority.
          There's probably others that I haven't thought of but if we capture them as subtasks at least we'll have traceability of them and we can allocate them to anyone who offers to volunteer some time.

          Show
          Chris Colman added a comment - - edited I'm hoping that this JIRA could be completed soon after recent emails in the mailing list. I have added some subtasks to capture some things that probably need doing, marking anything that prevents 'go live' with "Blocker" priority and all others that should not stop the go live as any other priority. There's probably others that I haven't thought of but if we capture them as subtasks at least we'll have traceability of them and we can allocate them to anyone who offers to volunteer some time.
          Hide
          Chris Colman added a comment -

          It looks like this fork from Chris J Lee has the most recent updates and implements a responsive design (using Foundation?):

          https://github.com/chrisjlee/wicket-site/tree/responsive

          Does it have everything required or do we need to integrate it with some more content from the original site source?

          We probably have to integrate the latest news items from the original site as the last changes to this fork were 6 months ago.

          If people agree this is the latest and funkiest should Chris' changes be pulled in to the master branch?

          Show
          Chris Colman added a comment - It looks like this fork from Chris J Lee has the most recent updates and implements a responsive design (using Foundation?): https://github.com/chrisjlee/wicket-site/tree/responsive Does it have everything required or do we need to integrate it with some more content from the original site source? We probably have to integrate the latest news items from the original site as the last changes to this fork were 6 months ago. If people agree this is the latest and funkiest should Chris' changes be pulled in to the master branch?
          Hide
          Martin Grigorov added a comment -

          Chris Colman Most people don't have the time and knowledge to setup this repo and see how the site looks like.
          To receive feedback I'd suggest to either collect some screenshots and share them (here, dropbox, ...) or add detailed description how to setup the repo locally.

          Show
          Martin Grigorov added a comment - Chris Colman Most people don't have the time and knowledge to setup this repo and see how the site looks like. To receive feedback I'd suggest to either collect some screenshots and share them (here, dropbox, ...) or add detailed description how to setup the repo locally.
          Hide
          Chris Colman added a comment -

          On windows I had to jump through a few hoops to install ruby and then run jekyll. Would certainly be easier if every person reviewing the new design didn't have to go through that.

          I was thinking maybe I could host the staging site on one of our spare servers so people could just go to the link to have a look instead of having to install ruby/jekyll etc.,

          Show
          Chris Colman added a comment - On windows I had to jump through a few hoops to install ruby and then run jekyll. Would certainly be easier if every person reviewing the new design didn't have to go through that. I was thinking maybe I could host the staging site on one of our spare servers so people could just go to the link to have a look instead of having to install ruby/jekyll etc.,
          Hide
          Chris Colman added a comment - - edited

          Correction!! The new site on github bitstorm does have the latest post - it is given prime place in the main panel on the left side - I was looking at the column on the right under "Older news" - Doh!

          So we can mark subtask https://issues.apache.org/jira/browse/WICKET-5765 as resolved also!

          Show
          Chris Colman added a comment - - edited Correction!! The new site on github bitstorm does have the latest post - it is given prime place in the main panel on the left side - I was looking at the column on the right under "Older news" - Doh! So we can mark subtask https://issues.apache.org/jira/browse/WICKET-5765 as resolved also!
          Hide
          Andrea Del Bene added a comment -

          Hi,

          all the useful informations to work with the site code are now available here: http://bitstorm.github.io/wicket-site/contribute/write.html. I hope they are clear enough. For posts and news we follow the standard convention of Jekyll: http://jekyllrb.com/docs/posts/

          Show
          Andrea Del Bene added a comment - Hi, all the useful informations to work with the site code are now available here: http://bitstorm.github.io/wicket-site/contribute/write.html . I hope they are clear enough. For posts and news we follow the standard convention of Jekyll: http://jekyllrb.com/docs/posts/
          Hide
          Chris Colman added a comment -

          It feels like we must be very close to 'go live' with the new site - exciting!

          Show
          Chris Colman added a comment - It feels like we must be very close to 'go live' with the new site - exciting!
          Hide
          Martijn Dashorst added a comment -

          I'd like to go through the site to see if I can actually build it, and I want to modify a couple of things:

          • no carousel
          • overview on main page
          • no ad for github (a commercial entity)
          • clearer how to contribute/get help
          • logo smaller and to the top left

          I can do some work tomorrow morning. While I appreciate the momentum, as one of the stakeholders I'd like to have a say as well.

          Show
          Martijn Dashorst added a comment - I'd like to go through the site to see if I can actually build it, and I want to modify a couple of things: no carousel overview on main page no ad for github (a commercial entity) clearer how to contribute/get help logo smaller and to the top left I can do some work tomorrow morning. While I appreciate the momentum, as one of the stakeholders I'd like to have a say as well.
          Hide
          Chris Colman added a comment -

          Hi Martijn, can I ask what you feel are the negative points about having the carousel? I find them useful to include a 'time shared' view of key information that would be awkward/crowded if placed all in one space as static content.

          Show
          Chris Colman added a comment - Hi Martijn, can I ask what you feel are the negative points about having the carousel? I find them useful to include a 'time shared' view of key information that would be awkward/crowded if placed all in one space as static content.
          Hide
          Andrea Del Bene added a comment -

          yeah, I also find carousel quite eye-catching and useful in the home page. Could you explain why you want to "kill" it ? I see other Apache projects using it as well, which of course doesn't mean we must do the same but I think it gives a fast overview of the project.
          And what about github? What would you like to remove? I agree we shouldn't ad any company, especially for free , but today it's very hard to involve other people without relying on github.

          Show
          Andrea Del Bene added a comment - yeah, I also find carousel quite eye-catching and useful in the home page. Could you explain why you want to "kill" it ? I see other Apache projects using it as well, which of course doesn't mean we must do the same but I think it gives a fast overview of the project. And what about github? What would you like to remove? I agree we shouldn't ad any company, especially for free , but today it's very hard to involve other people without relying on github.
          Hide
          Martijn Dashorst added a comment -

          Carousels are an anti pattern: to quote from an interview (http://www.creativebloq.com/accessibility-expert-warns-stop-using-carousels-7133778):

          > Carousels are seemingly an easy fix to two universal design problems: how do I fit
          > so much content into so little space, and how do I decide what content is the most
          > important? It's easy to justify away the usability issues of a carousel when you
          > consider the benefits of presenting multiple content pieces in such little real estate.
          > This has been exacerbated by unfounded focus on above-the-fold design.

          They are a cop-out: you can't decide what is the most important, so everything is important. And you hide (N-1)/N of the important stuff behind a wait until you see it (or you have to click through the list).

          It doesn't give a fast overview of something because it hides (N-1/N) of the content all the time.

          Why do you want a carousel? Because it is pretty? Because everybody has one? Because Bootstrap provides one? What do you want to achieve with the carousel? Why can't that goal not be attained with just plain visible content?

          As for Github: why not bitbucket, source forge, google code, and any other provider of git repositories? Why single out github on such a prominent place? They are not sponsors of the ASF, and the ASF even has less screen real estate. We are an ASF community after all, so we should be touting that instead of a direct link to a commercial entity's website.

          I like github, but I don't think it is the goal of and in the best interest of Wicket to promote github.

          Show
          Martijn Dashorst added a comment - Carousels are an anti pattern: to quote from an interview ( http://www.creativebloq.com/accessibility-expert-warns-stop-using-carousels-7133778): > Carousels are seemingly an easy fix to two universal design problems: how do I fit > so much content into so little space, and how do I decide what content is the most > important? It's easy to justify away the usability issues of a carousel when you > consider the benefits of presenting multiple content pieces in such little real estate. > This has been exacerbated by unfounded focus on above-the-fold design. They are a cop-out: you can't decide what is the most important, so everything is important. And you hide (N-1)/N of the important stuff behind a wait until you see it (or you have to click through the list). It doesn't give a fast overview of something because it hides (N-1/N) of the content all the time. Why do you want a carousel? Because it is pretty? Because everybody has one? Because Bootstrap provides one? What do you want to achieve with the carousel? Why can't that goal not be attained with just plain visible content? As for Github: why not bitbucket, source forge, google code, and any other provider of git repositories? Why single out github on such a prominent place? They are not sponsors of the ASF, and the ASF even has less screen real estate. We are an ASF community after all, so we should be touting that instead of a direct link to a commercial entity's website. I like github, but I don't think it is the goal of and in the best interest of Wicket to promote github.
          Hide
          Martin Grigorov added a comment - - edited

          /me likes the carousel as well.

          Agree with Andrea about GitHub.
          I don't see a link to a page "how to contribute code to Wicket" (something like http://wicket.apache.org/contribute/patch.html).
          GitHub may be a private company but it is a de facto standard these days.
          Many people asked for Atlassian Stash (or something similar that will provide easier Pull Request and code review) but Apache Infra refuses to setup it exactly for this reason - because most of the people who want to contribute to OS projects have account at GitHub and will not want to create an account at Apache's Stash. To me this is not serious because people create account at Apache JIRA to report issues.
          But until Infra does something I think we should try to make it easier for contributors. And the easiest IMO is to promote the GitHub mirror for PRs.

          Show
          Martin Grigorov added a comment - - edited /me likes the carousel as well. Agree with Andrea about GitHub. I don't see a link to a page "how to contribute code to Wicket" (something like http://wicket.apache.org/contribute/patch.html ). GitHub may be a private company but it is a de facto standard these days. Many people asked for Atlassian Stash (or something similar that will provide easier Pull Request and code review) but Apache Infra refuses to setup it exactly for this reason - because most of the people who want to contribute to OS projects have account at GitHub and will not want to create an account at Apache's Stash. To me this is not serious because people create account at Apache JIRA to report issues. But until Infra does something I think we should try to make it easier for contributors. And the easiest IMO is to promote the GitHub mirror for PRs.
          Hide
          Martijn Dashorst added a comment -

          There's a difference between having a prominent "... on GITHUB" in bright colors in the top right corner of our home page and having a link (with rel=no_follow) on a contribute to wicket page. The former is an ad, the latter is a helpful link on how to make it easier to contribute.

          Show
          Martijn Dashorst added a comment - There's a difference between having a prominent "... on GITHUB" in bright colors in the top right corner of our home page and having a link (with rel=no_follow) on a contribute to wicket page. The former is an ad, the latter is a helpful link on how to make it easier to contribute.
          Hide
          Martin Grigorov added a comment -

          "... on GitHub" is good enough for me.
          It seems you have missed this but http://wicket.apache.org/ has the ad since a while.

          About the carousel - I like it because it is visually catch-y.

          Show
          Martin Grigorov added a comment - "... on GitHub" is good enough for me. It seems you have missed this but http://wicket.apache.org/ has the ad since a while. About the carousel - I like it because it is visually catch-y.
          Hide
          Andrea Del Bene added a comment -

          Basically, I like carousel and "fork me" ribbon for the same reason: I think they improve project visibility and help to attract new contributors. I agree that carousel is not meant to give an overview of the project, but it works quite well as a fast "appetizer". Maybe it makes sense to link it to overview page.
          About the "fork me" ribbon, we can change its text with something more neutral without mentioning Github, if this can help.

          I'm adding you as contributor to the repository, so you can freely work on it.

          BTW: I worked to make the site look "decent" also on small devices, even if it's not the kind of site meant to be visited by those devices.

          Show
          Andrea Del Bene added a comment - Basically, I like carousel and "fork me" ribbon for the same reason: I think they improve project visibility and help to attract new contributors. I agree that carousel is not meant to give an overview of the project, but it works quite well as a fast "appetizer". Maybe it makes sense to link it to overview page. About the "fork me" ribbon, we can change its text with something more neutral without mentioning Github, if this can help. I'm adding you as contributor to the repository, so you can freely work on it. BTW: I worked to make the site look "decent" also on small devices, even if it's not the kind of site meant to be visited by those devices.
          Hide
          chrisjlee added a comment - - edited

          Sorry i've fallen off of this effort. I've just wrapped up some projects and i'd like to help again.

          Andrea Del Bene where are the changes you're making? Are they in a particular github repository? I can contribute and help in any way. I just don't want some of the work i've done to go to the wayside.

          Show
          chrisjlee added a comment - - edited Sorry i've fallen off of this effort. I've just wrapped up some projects and i'd like to help again. Andrea Del Bene where are the changes you're making? Are they in a particular github repository? I can contribute and help in any way. I just don't want some of the work i've done to go to the wayside.
          Hide
          Andrea Del Bene added a comment -

          Hi Chris and thank you again for your excellent work! I forked your repo here: https://github.com/bitstorm/wicket-site. I've added you as contributor. I decide to fork your work repo because I had some time to spend on it and I didn't know if you were able to continue to work on it.
          Your original index.html page has been renamed to single.html.

          PS: do we still need foundation.js? AFAICS we don't actually use it....

          Show
          Andrea Del Bene added a comment - Hi Chris and thank you again for your excellent work! I forked your repo here: https://github.com/bitstorm/wicket-site . I've added you as contributor. I decide to fork your work repo because I had some time to spend on it and I didn't know if you were able to continue to work on it. Your original index.html page has been renamed to single.html. PS: do we still need foundation.js? AFAICS we don't actually use it....
          Hide
          Chris Colman added a comment -

          Martijn Dashorst Do you believe that any/all of the issues that you raised:

          • no carousel
          • overview on main page
          • no ad for github (a commercial entity)
          • clearer how to contribute/get help
          • logo smaller and to the top left

          should be regarded as showstoppers/blockers preventing the upgrade to the new website or could we go ahead with the new website and deal with the above issues after the update?

          I'm just concerned that while ever we keep the old styling we're not doing Wicket justice for the reasons many have discussed since this ticket was raised in January 2011 - I have just demo'd a wicket-bootstrap app that we built for a client and they loved it because it looks so sexy and modern and it's full of slick, AJAX/partial page updates - and all via Java - their company language. I think this client could really benefit from doing their own in-house development using wicket as well but I'm holding out on sending them to the wicket home page until the styling/layout is upgraded

          I think that moving to the updated site now still represents a net positive that represents a x10^6 improvement - even with the issues you raise - which, to my thinking at least, could be dealt with after the new site is live as I don't think any of the issues that you raise, if they persisted only for the immediate short term, represent a risk to reputation or image.

          Show
          Chris Colman added a comment - Martijn Dashorst Do you believe that any/all of the issues that you raised: no carousel overview on main page no ad for github (a commercial entity) clearer how to contribute/get help logo smaller and to the top left should be regarded as showstoppers/blockers preventing the upgrade to the new website or could we go ahead with the new website and deal with the above issues after the update? I'm just concerned that while ever we keep the old styling we're not doing Wicket justice for the reasons many have discussed since this ticket was raised in January 2011 - I have just demo'd a wicket-bootstrap app that we built for a client and they loved it because it looks so sexy and modern and it's full of slick, AJAX/partial page updates - and all via Java - their company language. I think this client could really benefit from doing their own in-house development using wicket as well but I'm holding out on sending them to the wicket home page until the styling/layout is upgraded I think that moving to the updated site now still represents a net positive that represents a x10^6 improvement - even with the issues you raise - which, to my thinking at least, could be dealt with after the new site is live as I don't think any of the issues that you raise, if they persisted only for the immediate short term, represent a risk to reputation or image.
          Hide
          Martijn Dashorst added a comment -

          While I appreciate the work that went into it, I am seriously against any carousel, and this one in particular because it doesn't make the design better, it makes it worse. There are several reasons why I want to kill it before it hits apache.org

          • my design does not feature one. I deliberately did not add a carousel.
          • my graphics are unsuited for being part of the carousel: they are fuzzy, under-designed, have too little detail, are crude
          • hence it makes the site look amateurish
          • the carousel doesn't add anything to the page other than some movement
          • thus I have to wait some indeterminate time or click on buttons for new content
          • the content is just bland: it is just a heading without any context or content.
          • Carousels are inherently awful for accessibility. They require javascript, change content on a whim and don't add value for non-visual browsers.

          This is not how I designed the page. I deliberately didn't design a carousel in the pages. I did it once for an earlier concept showing sites that use Wicket, but I didn't like it. Reading up on carousels further cemented my opinion that they are evil and should be banned.

          I want our front page to be deliberate, to have an air of maturity, to strive to be non-buzzwordy. If we claim something I want us to back it up. Anyone can say "We're secure by default"–we can back it up. If I see a website with just the claim and nothing to back it up I assume it is just doing lip service and a marketing person wrote it up because they saw it on another web site.

          Show
          Martijn Dashorst added a comment - While I appreciate the work that went into it, I am seriously against any carousel, and this one in particular because it doesn't make the design better, it makes it worse. There are several reasons why I want to kill it before it hits apache.org my design does not feature one. I deliberately did not add a carousel. my graphics are unsuited for being part of the carousel: they are fuzzy, under-designed, have too little detail, are crude hence it makes the site look amateurish the carousel doesn't add anything to the page other than some movement thus I have to wait some indeterminate time or click on buttons for new content the content is just bland: it is just a heading without any context or content. Carousels are inherently awful for accessibility. They require javascript, change content on a whim and don't add value for non-visual browsers. This is not how I designed the page. I deliberately didn't design a carousel in the pages. I did it once for an earlier concept showing sites that use Wicket, but I didn't like it. Reading up on carousels further cemented my opinion that they are evil and should be banned. I want our front page to be deliberate, to have an air of maturity, to strive to be non-buzzwordy. If we claim something I want us to back it up. Anyone can say "We're secure by default"–we can back it up. If I see a website with just the claim and nothing to back it up I assume it is just doing lip service and a marketing person wrote it up because they saw it on another web site.
          Hide
          Martijn Dashorst added a comment -

          Yes I regard them as showstoppers. Because I think the new site is only prettier, not better. It has less necessary information. There are lots of flaws in the design I envisioned, and its current implementation. The momentum we have for developing a new site is great and we need to keep that going, but force publishing it now when I have legitimate concerns makes me feel under appreciated and under valued.

          If the issue has been open since 2011, why is it adamant to go and force publishing the site right now, aggravate me in the process–while we can work on the issues, include more people in the process, have everybody mostly happy and publish a new, improved web site in a couple of days or weeks?

          And I think the github banner is actually against the website policy, if not in writing most certainly in spirit. I want it not only gone from the new design, but also from the current website ASAP.

          Show
          Martijn Dashorst added a comment - Yes I regard them as showstoppers. Because I think the new site is only prettier, not better. It has less necessary information. There are lots of flaws in the design I envisioned, and its current implementation. The momentum we have for developing a new site is great and we need to keep that going, but force publishing it now when I have legitimate concerns makes me feel under appreciated and under valued. If the issue has been open since 2011, why is it adamant to go and force publishing the site right now, aggravate me in the process–while we can work on the issues, include more people in the process, have everybody mostly happy and publish a new, improved web site in a couple of days or weeks? And I think the github banner is actually against the website policy, if not in writing most certainly in spirit. I want it not only gone from the new design, but also from the current website ASAP.
          Hide
          Martijn Dashorst added a comment -

          Non content related issues:

          • scss: does it work or not? If it should work, how can I trigger an update from scss to css file?
          • bower.json, package.json, Gemfile, why are these files necessary?
          • (s)css is one big giant bundle

          I have no experience with scss/compass but I know that those can and should be set up modularly, not as one big css file. Personally I favor lessjs but since we already have a ruby build (jekyllrb) scss might not be a bad alternative (both lessjs and scss are similar in provided functionality)

          I see a lot of different technologies in the project, and have no idea which ones are used or just added as an experiment. Why do we need bower, etc.?

          Show
          Martijn Dashorst added a comment - Non content related issues: scss: does it work or not? If it should work, how can I trigger an update from scss to css file? bower.json, package.json, Gemfile, why are these files necessary? (s)css is one big giant bundle I have no experience with scss/compass but I know that those can and should be set up modularly, not as one big css file. Personally I favor lessjs but since we already have a ruby build (jekyllrb) scss might not be a bad alternative (both lessjs and scss are similar in provided functionality) I see a lot of different technologies in the project, and have no idea which ones are used or just added as an experiment. Why do we need bower, etc.?
          Hide
          Andrea Del Bene added a comment -

          I use to regenerate css running 'sass --scss ./scss/main.scss ./css/main.css' on the project root. But I don't know if Chris meant to do it like this...
          For the other technologies involved so far I think we should ask to Chris as well. In the end it would be nice (although not necessary) to have a working gulp-based configuration to handle the entire project (fetching dependencies, running jekyll, etc...).

          Show
          Andrea Del Bene added a comment - I use to regenerate css running 'sass --scss ./scss/main.scss ./css/main.css' on the project root. But I don't know if Chris meant to do it like this... For the other technologies involved so far I think we should ask to Chris as well. In the end it would be nice (although not necessary) to have a working gulp-based configuration to handle the entire project (fetching dependencies, running jekyll, etc...).
          Hide
          Andrea Del Bene added a comment -

          There is of course no hurry to publish a new site. However, with Wicket 7 around the corner it would be a huge shame not to take this chance ad give additional boost to Wicket with a new site. We can simply remove the carousel if we don't have an unanimous decision about it.
          But I don't fully understand your concerns about the github banner. Github is now the 'de facto' standard for open source projects to collaborate and attract contributors and I think it gives Wicket more visibility. The ASF itself has mirrored all the git repos inside GitHub, so I don't see any violation of web policy or of the project aims.

          Show
          Andrea Del Bene added a comment - There is of course no hurry to publish a new site. However, with Wicket 7 around the corner it would be a huge shame not to take this chance ad give additional boost to Wicket with a new site. We can simply remove the carousel if we don't have an unanimous decision about it. But I don't fully understand your concerns about the github banner. Github is now the 'de facto' standard for open source projects to collaborate and attract contributors and I think it gives Wicket more visibility. The ASF itself has mirrored all the git repos inside GitHub, so I don't see any violation of web policy or of the project aims.
          Hide
          Martijn Dashorst added a comment -

          Linking to github in such a visible and prominent way is in violation of policy. The Wicket community is an apache community. No matter what happens in the outside world, We Are An Apache Community Foremost. Number 1: Apache. The ASF. wicket.apache.org. NOT github. Not a commercial entity. We must not link on every page to github. We must not provide a banner with Github prominently on our pages.

          How many times do I need to say this? In what way can I make it more clear that it is not acceptable to give github a prominent ad banner on our non-profit website? A direct link to a commercial entity on all our pages, right in your face?

          Show
          Martijn Dashorst added a comment - Linking to github in such a visible and prominent way is in violation of policy. The Wicket community is an apache community. No matter what happens in the outside world, We Are An Apache Community Foremost. Number 1: Apache. The ASF. wicket.apache.org. NOT github. Not a commercial entity. We must not link on every page to github. We must not provide a banner with Github prominently on our pages. How many times do I need to say this? In what way can I make it more clear that it is not acceptable to give github a prominent ad banner on our non-profit website? A direct link to a commercial entity on all our pages, right in your face?
          Hide
          Martijn Dashorst added a comment -

          As for the carousel: I'd rather use our "built with Wicket" tumblr posts for a carousel showcasing projects that use Wicket. We can use http://stackoverflow.com/questions/25495485/how-do-i-display-a-carousel-of-embedded-tumblr-posts for that. This combines two things:

          1. image content that is suitable for a carousel (sometimes refreshed content)

          2. the content of "built with wicket" has a good place to go instead of being 'forgotten' at tumblr

          This makes it more attractive to find contributions for builtwithwicket and we have a good place to show it. Added bonus: the screenshots are typically of high enough quality to be in a carousel showing 1-3 posts at a time without getting pixelated.

          Show
          Martijn Dashorst added a comment - As for the carousel: I'd rather use our "built with Wicket" tumblr posts for a carousel showcasing projects that use Wicket. We can use http://stackoverflow.com/questions/25495485/how-do-i-display-a-carousel-of-embedded-tumblr-posts for that. This combines two things: 1. image content that is suitable for a carousel (sometimes refreshed content) 2. the content of "built with wicket" has a good place to go instead of being 'forgotten' at tumblr This makes it more attractive to find contributions for builtwithwicket and we have a good place to show it. Added bonus: the screenshots are typically of high enough quality to be in a carousel showing 1-3 posts at a time without getting pixelated.
          Hide
          Andrea Del Bene added a comment -

          I think it's an excellent idea! As side note: I had already added a link to "built with wicket" at the end of friends page. I did it because I also have the feeling that the tumblr page is being ignored...

          Show
          Andrea Del Bene added a comment - I think it's an excellent idea! As side note: I had already added a link to "built with wicket" at the end of friends page. I did it because I also have the feeling that the tumblr page is being ignored...
          Hide
          chrisjlee added a comment - - edited

          I don't think the JS file is used at the moment. But i would test it though to be sure. I think it would be used for the mobile menu.

          The thought would be to use the foundation front end framework; so that we can utilize the responsive grids, the mobile menu, etc.

          The sass / scss hasn't been setup and integrated. I can do that.

          Show
          chrisjlee added a comment - - edited I don't think the JS file is used at the moment. But i would test it though to be sure. I think it would be used for the mobile menu. The thought would be to use the foundation front end framework; so that we can utilize the responsive grids, the mobile menu, etc. The sass / scss hasn't been setup and integrated. I can do that.
          Hide
          Martijn Dashorst added a comment -

          My current focus for developing on the site is in the dashorst branch. sass works out of the box without any additional installations required (AFAIK)–it is picked up by jekyllrb.

          I have used a custom responsive grid framework that is just in the _sass/taiga folder without the need to manage dependencies. I doubt we need more than what is provided by this barebones grid. The code implementing the grid is easy to follow.

          The logo has been vectorized so it renders great on all resolutions.

          Things to do:

          • I want the sub pages to have a slimmer header (move logo to left side, menu to right side)
          • carousel for tumblr (but we can go live without that one)
          • evaluate the menu structure (naming of menu items)
          • re-organize content so it fits in the menu structure (quickstart/download/...)
          • think about how to address wicket 1.5.x, wicket 6.x, wicket 7.x and wicket 8.x documentation and download sections
          • construct deep linking footer for quick navigation
          • move the /2010/... news items to /blog/2010 (or /news/2010) subfolders
          • generate index pages for /[blog|news]/2010 and /[blog|news]/2010/2 pages
          • test in firefox/IE/mobile
          • generate .htaccess files for redirecting/rewriting non-existing URLs to new location of files
          • remove unnecessary files (e.g. the examples articles)
          Show
          Martijn Dashorst added a comment - My current focus for developing on the site is in the dashorst branch. sass works out of the box without any additional installations required (AFAIK)–it is picked up by jekyllrb. I have used a custom responsive grid framework that is just in the _sass/taiga folder without the need to manage dependencies. I doubt we need more than what is provided by this barebones grid. The code implementing the grid is easy to follow. The logo has been vectorized so it renders great on all resolutions. Things to do: I want the sub pages to have a slimmer header (move logo to left side, menu to right side) carousel for tumblr (but we can go live without that one) evaluate the menu structure (naming of menu items) re-organize content so it fits in the menu structure (quickstart/download/...) think about how to address wicket 1.5.x, wicket 6.x, wicket 7.x and wicket 8.x documentation and download sections construct deep linking footer for quick navigation move the /2010/... news items to /blog/2010 (or /news/2010) subfolders generate index pages for / [blog|news] /2010 and / [blog|news] /2010/2 pages test in firefox/IE/mobile generate .htaccess files for redirecting/rewriting non-existing URLs to new location of files remove unnecessary files (e.g. the examples articles)
          Hide
          Chris Colman added a comment -

          By 'custom responsive grid' do you mean a 'home grown' responsive grid?

          Foundation and Bootstrap are both here to stay and both do an incredibly good job and many Java developers know either one or both of them. I'm not sure what the advantage is in working on a home grown responsive grid when these others have communities of developers maintaining them and adding all of the browser independence, responsiveness etc., that we know already works and has been tested on literally millions (Bootstrap powered sites number about ~3.7 million http://trends.builtwith.com/docinfo/Twitter-Bootstrap) already.

          I understand the argument that they 'can' look familiar but that is just due to lazy people using the defaults. It is totally customizable in .less or .scss and there a plenty of free examples (especially for bootstrap) that look completely awesome and completely different to the default.

          Is there a preview available for your dashorst branch? Is that the PDF that you mention the readme.md?

          Show
          Chris Colman added a comment - By 'custom responsive grid' do you mean a 'home grown' responsive grid? Foundation and Bootstrap are both here to stay and both do an incredibly good job and many Java developers know either one or both of them. I'm not sure what the advantage is in working on a home grown responsive grid when these others have communities of developers maintaining them and adding all of the browser independence, responsiveness etc., that we know already works and has been tested on literally millions (Bootstrap powered sites number about ~3.7 million http://trends.builtwith.com/docinfo/Twitter-Bootstrap ) already. I understand the argument that they 'can' look familiar but that is just due to lazy people using the defaults. It is totally customizable in .less or .scss and there a plenty of free examples (especially for bootstrap) that look completely awesome and completely different to the default. Is there a preview available for your dashorst branch? Is that the PDF that you mention the readme.md?
          Hide
          chrisjlee added a comment -

          I would agree with Chris Colman. Although, i'd want to stray away from bootstrap because it's too cookie cutter and will look like other sites.

          Also, IMHO foundation's grid is more robust.

          Show
          chrisjlee added a comment - I would agree with Chris Colman. Although, i'd want to stray away from bootstrap because it's too cookie cutter and will look like other sites. Also, IMHO foundation's grid is more robust.
          Hide
          Chris Colman added a comment -

          I have used both Foundation and Bootstrap. Given Chris J Lee's branch is already using Foundation then, for expediency, I'd prefer we use Foundation.

          Show
          Chris Colman added a comment - I have used both Foundation and Bootstrap. Given Chris J Lee's branch is already using Foundation then, for expediency, I'd prefer we use Foundation.
          Hide
          Martijn Dashorst added a comment -

          Preview that uses just plain old jekyll and no extra plugins (this way it works on github pages):

          http://dashorst.github.io/wicket-site

          Note that I only worked on the front page for now, and that the tumblr carousel is not yet working.

          Show
          Martijn Dashorst added a comment - Preview that uses just plain old jekyll and no extra plugins (this way it works on github pages): http://dashorst.github.io/wicket-site Note that I only worked on the front page for now, and that the tumblr carousel is not yet working.
          Hide
          Chris Colman added a comment - - edited

          On FF and Chrome this site:
          http://dashorst.github.io/wicket-site
          has the large title text APACHE WICKET overlapping. The 'W' in wicket starts halfway through the 'H' in APACHE. I haven't tried it in IE.
          There is also a mix of serif and non serif fonts. I'm no graphic artist but in the graphic arts world, so I've been told, mixing serif and san serif font's is the equivalent of using 'goto' in the programming world
          These typography glitches and scope for breaking the fundamental (but largely unknown by developers) graphics "laws" when it comes to typography are extremely rare when you use an off the shelf grid template like Foundation or Bootstrap.

          Show
          Chris Colman added a comment - - edited On FF and Chrome this site: http://dashorst.github.io/wicket-site has the large title text APACHE WICKET overlapping. The 'W' in wicket starts halfway through the 'H' in APACHE. I haven't tried it in IE. There is also a mix of serif and non serif fonts. I'm no graphic artist but in the graphic arts world, so I've been told, mixing serif and san serif font's is the equivalent of using 'goto' in the programming world These typography glitches and scope for breaking the fundamental (but largely unknown by developers) graphics "laws" when it comes to typography are extremely rare when you use an off the shelf grid template like Foundation or Bootstrap.
          Hide
          chrisjlee added a comment -

          So which fork is the latest fork that we should work on? This one right? https://github.com/bitstorm/wicket-site With the responsive branch?

          Show
          chrisjlee added a comment - So which fork is the latest fork that we should work on? This one right? https://github.com/bitstorm/wicket-site With the responsive branch?
          Hide
          Martijn Dashorst added a comment -

          The fonts are off because of missing @fontface definitions. Furthermore the SVG logo appears not to pick up the font definition for League Gothic. I'm investigating this particular issue as it was hidden from me due to having the fonts installed on my system.

          Show
          Martijn Dashorst added a comment - The fonts are off because of missing @fontface definitions. Furthermore the SVG logo appears not to pick up the font definition for League Gothic. I'm investigating this particular issue as it was hidden from me due to having the fonts installed on my system.
          Hide
          Martijn Dashorst added a comment -

          I've updated the logo with an embedded League Gothic font (base64 encoded), but I'd rather just include the SVG elements we use, but my SVG fu is not strong enough to get that to work. The site should now render as intended.

          Show
          Martijn Dashorst added a comment - I've updated the logo with an embedded League Gothic font (base64 encoded), but I'd rather just include the SVG elements we use, but my SVG fu is not strong enough to get that to work. The site should now render as intended.
          Hide
          Martijn Dashorst added a comment -

          I've improved the smoothness of the responsive break points when resizing (though not many folks will constantly resize their browser), SVG logo now works as advertised, I've fixed some layout issues with the subpages, added more links to sub pages in the menu bar, fixed an issue with bad rendering of an external link (http://www.apache.org).

          As an experiment I modified the jumbotron to show a black/white, vignetted photo of the first Wicket meetup in early 2005. I like the homage to the original team considering our 10 year anniversary. But I can also see that it might be a bit distracting.

          You can see it all in action at http://dashorst.github.io/wicket-site

          Show
          Martijn Dashorst added a comment - I've improved the smoothness of the responsive break points when resizing (though not many folks will constantly resize their browser), SVG logo now works as advertised, I've fixed some layout issues with the subpages, added more links to sub pages in the menu bar, fixed an issue with bad rendering of an external link ( http://www.apache.org ). As an experiment I modified the jumbotron to show a black/white, vignetted photo of the first Wicket meetup in early 2005. I like the homage to the original team considering our 10 year anniversary. But I can also see that it might be a bit distracting. You can see it all in action at http://dashorst.github.io/wicket-site
          Hide
          Andrea Del Bene added a comment -

          I think the new jumbotron is really cool! What about the 'friends' page? I think it should be used also to link third part open source libraries like WicketStuff and JQuery/Bootstrap or whatever integrations.

          Show
          Andrea Del Bene added a comment - I think the new jumbotron is really cool! What about the 'friends' page? I think it should be used also to link third part open source libraries like WicketStuff and JQuery/Bootstrap or whatever integrations.
          Hide
          Martijn Dashorst added a comment -

          The site is not finished at all, so I just put some stop gap measures in to have non-failing navigation (I couldn't find a suitable page for news though).

          My intention is to repurpose the Apache link in the menu and make a page with some columns for our Apache friends and a short description and link to the ASF main website and specific resources of the foundation.

          The navigation is still an unresolved issue IMO. What content goes under which menu item, and even which menu items we should have... For example: is a news menu item necessary? Or a Downloads menu item?

          WicketStuff and other projects (e.g. bootstrap) can go under all Download, Documentation and Contribute sections (at the same time).

          I'd like to use the maven-site-plugin for generating branch specific websites with downloads, user manual documentation and API docs. This could be under a Releases menu item (in stead of Documentation and Download). This can be hooked up in buildbot and generated with each snapshot (have a <wicket.stable.version> in the properties section and use that to provide links to a download). This way we have up-to-date documentation and release information. Unfortunately this also means that the download links would be two clicks away.

          Menu structure:

          News (necessary? replace with Overview?)

          • index with latest 10 news items, side menu with archive links
          • link to announce list
          • sub pages for each year
          • sub pages for each month

          Start ?

          • index with:
          • quickstart panel
          • documentation link to user manual
          • our own projects (brief descriptions)
          • friend projects
          • ...?

          Releases

          • index with description of the various branches
          • direct links to downloads, documentation and API docs of latest versions of branches
          • side menu with links to buildbot generated sub sites for each active branch

          Support

          • index with support options (user list, irc, stack overflow, report an issue)

          Contribute

          • link to our source repository, issue tracker, buildbot, dev list
          • description of how to contribute (patch, PR at github, ...)
          • how to become a committer
          • coding guidelines

          Apache

          • index with friends projects at apache
          • description of Apache and links to various places (sponsors, ...)

          How does this sound?

          Show
          Martijn Dashorst added a comment - The site is not finished at all, so I just put some stop gap measures in to have non-failing navigation (I couldn't find a suitable page for news though). My intention is to repurpose the Apache link in the menu and make a page with some columns for our Apache friends and a short description and link to the ASF main website and specific resources of the foundation. The navigation is still an unresolved issue IMO. What content goes under which menu item, and even which menu items we should have... For example: is a news menu item necessary? Or a Downloads menu item? WicketStuff and other projects (e.g. bootstrap) can go under all Download, Documentation and Contribute sections (at the same time). I'd like to use the maven-site-plugin for generating branch specific websites with downloads, user manual documentation and API docs. This could be under a Releases menu item (in stead of Documentation and Download). This can be hooked up in buildbot and generated with each snapshot (have a <wicket.stable.version> in the properties section and use that to provide links to a download). This way we have up-to-date documentation and release information. Unfortunately this also means that the download links would be two clicks away. Menu structure: News (necessary? replace with Overview?) index with latest 10 news items, side menu with archive links link to announce list sub pages for each year sub pages for each month Start ? index with: quickstart panel documentation link to user manual our own projects (brief descriptions) friend projects ...? Releases index with description of the various branches direct links to downloads, documentation and API docs of latest versions of branches side menu with links to buildbot generated sub sites for each active branch Support index with support options (user list, irc, stack overflow, report an issue) Contribute link to our source repository, issue tracker, buildbot, dev list description of how to contribute (patch, PR at github, ...) how to become a committer coding guidelines Apache index with friends projects at apache description of Apache and links to various places (sponsors, ...) How does this sound?
          Hide
          Andrea Del Bene added a comment -

          Personally I don't think we need a news page as long as we keep the "classic" home page with a short project description and the news as following content. The menu structure you proposed looks good to me.
          Having a maven-based generating mechanism would be a great idea as well, but at the moment I'm not very familiar with it. Do you think it's gonna take a long time to set up the entire thing or should we go haed with the new site and then focus on this other task?

          Show
          Andrea Del Bene added a comment - Personally I don't think we need a news page as long as we keep the "classic" home page with a short project description and the news as following content. The menu structure you proposed looks good to me. Having a maven-based generating mechanism would be a great idea as well, but at the moment I'm not very familiar with it. Do you think it's gonna take a long time to set up the entire thing or should we go haed with the new site and then focus on this other task?
          Hide
          Martijn Dashorst added a comment -

          I've updated the version on http://dashorst.github.io/wicket-site to include archive pages of news (see http://dashorst.github.io/wicket-site/news). It took some hacking of jekyll plugins to get it to work, but now years and months have archive pages (http://dashorst.github.io/wicket-site/news/2014 and http://dashorst.github.io/wicket-site/news/2014/11)

          Show
          Martijn Dashorst added a comment - I've updated the version on http://dashorst.github.io/wicket-site to include archive pages of news (see http://dashorst.github.io/wicket-site/news ). It took some hacking of jekyll plugins to get it to work, but now years and months have archive pages ( http://dashorst.github.io/wicket-site/news/2014 and http://dashorst.github.io/wicket-site/news/2014/11 )
          Hide
          Martijn Dashorst added a comment -

          Regarding the github banner: the discussion on board@ has subsided and there are varying opinions, some stated they wouldn't mind, others would mind. Which doesn't mean it is a free for all.

          Re-reading the relevant section from our marks policy/guidelines (http://www.apache.org/foundation/marks/linking#projectthanks) tells me that we should not link to github directly from all our pages (including the front page). The guidelines specifically state:

          > Project Thanks Pages / Listings:
          > [...]
          > * Should not be on the project's home page.

          And

          > PMCs may choose to provide relevant listings of other useful
          > websites within their larger ecosystem, as a service to the
          > project's users. Such listings may include factual links to outside
          > organizations offering support, training, hosting, or other similar
          > services related to that Apache project.
          >
          > [...]
          > * Should not be on the project homepage, only on a secondary
          > page on the project website. Placing prominent links to third party
          > services or products on the homepage of a project is often seen
          > by new users as an advertisement, and an implicit endorsement
          > of that service or product by Apache, which is probably not what
          > we intend.

          So this is the policy.

          In my personal opinion, major linkage to github on our homepage is telling
          folks "Hey we are not here at Apache, but we are over there! Don't join us
          at Apache, but do a drive-by at github. YOLO".

          If we were to have a banner (note the *if*) it should link to our contribute
          page where we lay down the list of ways someone can contribute:

          • patch through jira/mailinglist
          • PR at github
          • ... etc
            The banner could say "Contribute to Wicket", "Join Wicket", or something
            else catchy. That said, I think such a banner would not be beneficial to our
            website nor our community.
          Show
          Martijn Dashorst added a comment - Regarding the github banner: the discussion on board@ has subsided and there are varying opinions, some stated they wouldn't mind, others would mind. Which doesn't mean it is a free for all. Re-reading the relevant section from our marks policy/guidelines ( http://www.apache.org/foundation/marks/linking#projectthanks ) tells me that we should not link to github directly from all our pages (including the front page). The guidelines specifically state: > Project Thanks Pages / Listings: > [...] > * Should not be on the project's home page. And > PMCs may choose to provide relevant listings of other useful > websites within their larger ecosystem, as a service to the > project's users. Such listings may include factual links to outside > organizations offering support, training, hosting, or other similar > services related to that Apache project. > > [...] > * Should not be on the project homepage, only on a secondary > page on the project website. Placing prominent links to third party > services or products on the homepage of a project is often seen > by new users as an advertisement, and an implicit endorsement > of that service or product by Apache, which is probably not what > we intend. So this is the policy. In my personal opinion, major linkage to github on our homepage is telling folks "Hey we are not here at Apache, but we are over there! Don't join us at Apache, but do a drive-by at github. YOLO". If we were to have a banner (note the * if *) it should link to our contribute page where we lay down the list of ways someone can contribute: patch through jira/mailinglist PR at github ... etc The banner could say "Contribute to Wicket", "Join Wicket", or something else catchy. That said, I think such a banner would not be beneficial to our website nor our community.
          Hide
          Martin Grigorov added a comment -

          I thought the discussion with the board didn't happen because there was no response from them to your email.
          But this is not something new to Apache ... "Open" has its own meaning here :-/

          Let's call a vote at dev@ and count who is OK to have a banner/page and who is against.
          I think this is the most democratic way.

          Pull Requests at GitHub/BitBucket/YouNameIt is much easier way for a user to contribute and for me as a Wicket member to review and apply.
          Apache Board and Infra team were (and many of them still are) against using Git in first place. They prefer SVN/CVS...
          By providing mirrors for both Git and SVN projects at GitHub I think Apache has already made a really big step!
          On the other side the Apache Git repo url stil says "WIP" (https://git-wip-us.apache.org/repos/asf/wicket.git) !

          If we want to move on then we should adapt. GitHub is not something new, it is not just a hype. It is a model that proved itself as working. It could be the age of Wicket or our resistance to adapt/evolve but everyone can tell you that in the last years the number of contributions decreases. We could stay and wait for a miracle to happen or try to make something!

          Show
          Martin Grigorov added a comment - I thought the discussion with the board didn't happen because there was no response from them to your email. But this is not something new to Apache ... "Open" has its own meaning here :-/ Let's call a vote at dev@ and count who is OK to have a banner/page and who is against. I think this is the most democratic way. Pull Requests at GitHub/BitBucket/YouNameIt is much easier way for a user to contribute and for me as a Wicket member to review and apply. Apache Board and Infra team were (and many of them still are) against using Git in first place. They prefer SVN/CVS... By providing mirrors for both Git and SVN projects at GitHub I think Apache has already made a really big step! On the other side the Apache Git repo url stil says "WIP" ( https://git-wip-us.apache.org/repos/asf/wicket.git ) ! If we want to move on then we should adapt. GitHub is not something new, it is not just a hype. It is a model that proved itself as working. It could be the age of Wicket or our resistance to adapt/evolve but everyone can tell you that in the last years the number of contributions decreases. We could stay and wait for a miracle to happen or try to make something!
          Hide
          Martijn Dashorst added a comment -

          How does it follow that we can't use Github from not having a "fork me at github" link on all our pages?

          Show
          Martijn Dashorst added a comment - How does it follow that we can't use Github from not having a "fork me at github" link on all our pages?
          Hide
          Andrea Del Bene added a comment -

          In my personal opinion, major linkage to github on our homepage is telling
          folks "Hey we are not here at Apache, but we are over there! Don't join us
          at Apache, but do a drive-by at github. YOLO".

          Right, but Apache is a membership based organization and that's great, but honestly if you are out of it you have very few chances to contribute to projects. As also Martin said Github is today a model for many people and we should embrace it. That said, as Apache project we will keep ourself indipendent from GitHub and if tomorrow for any reason we will decide to move away from it, we can do it without any problem.

          If we were to have a banner (note the if) it should link to our contribute
          page where we lay down the list of ways someone can contribute
          ....
          The banner could say "Contribute to Wicket", "Join Wicket", or something
          else catchy. That said, I think such a banner would not be beneficial to our
          website nor our community.

          that's whould be perfect for me.

          Show
          Andrea Del Bene added a comment - In my personal opinion, major linkage to github on our homepage is telling folks "Hey we are not here at Apache, but we are over there! Don't join us at Apache, but do a drive-by at github. YOLO". Right, but Apache is a membership based organization and that's great, but honestly if you are out of it you have very few chances to contribute to projects. As also Martin said Github is today a model for many people and we should embrace it. That said, as Apache project we will keep ourself indipendent from GitHub and if tomorrow for any reason we will decide to move away from it, we can do it without any problem. If we were to have a banner (note the if ) it should link to our contribute page where we lay down the list of ways someone can contribute .... The banner could say "Contribute to Wicket", "Join Wicket", or something else catchy. That said, I think such a banner would not be beneficial to our website nor our community. that's whould be perfect for me.
          Hide
          Martin Grigorov added a comment -

          You removed the "fork me at ..." link but you didn't provide an alternative.
          http://wicket.apache.org/contribute/patch.html says nothing about alternatives.

          Additionally you suggest to not have a quick link to "How to contribute" page in the new site with "That said, I think such a banner would not be beneficial to our website nor our community.".
          So I suggest to vote about such kind of decisions.

          In this ticket's comments no one but you was against the banner. Apparently there are even board members which don't find a problem with it.

          Having a "How to contribute" page (and a banner as a quick link to it) would be the best, IMO.
          But just removing something because you feel it is not correct without providing an alternative doesn't look correct to me.

          Show
          Martin Grigorov added a comment - You removed the "fork me at ..." link but you didn't provide an alternative. http://wicket.apache.org/contribute/patch.html says nothing about alternatives. Additionally you suggest to not have a quick link to "How to contribute" page in the new site with "That said, I think such a banner would not be beneficial to our website nor our community.". So I suggest to vote about such kind of decisions. In this ticket's comments no one but you was against the banner. Apparently there are even board members which don't find a problem with it. Having a "How to contribute" page (and a banner as a quick link to it) would be the best, IMO. But just removing something because you feel it is not correct without providing an alternative doesn't look correct to me.
          Hide
          Michael Mosmann added a comment - - edited

          I am not sure if I understand everyone’s position. That's why I will ask some (maybe stupid) questions:

          • Do we want more contributions from people which are not part of the apache foundation?
            If "yes":
            • What kind of options are possible?
            • Do we prefer some of these options?
            • Are there any benefits from one over the others?
            • Are there any risks in any of these options?
              If "no":
            • Why?
          • Do we want more contributons from people which are part of the apache foundation?
            If "yes":
            • How can we achieve this?
          • Are there any benefits using github?
            If "yes":
            • How can we compete using the existing apache infrastructure?
            • How must we improve to live happy without github?
            • How long does it take?
          • Are there any risks using github?
            If "yes":
            • Which kind of risk?
            • Can we reduce risks in any way?
          • Is there any conflict with apache guidlines/legal/... using github at all?

          personal note:
          If I have to vote, it would not be easy for me to come to a clear conclusion. As I understand martijn, this is an apache project and we should honour this as good as we can. I understand martin and the others as they hope that we can attract more people to contribute and to use wicket more and more. It would surprise me, if we can not achieve both.

          Michael

          Show
          Michael Mosmann added a comment - - edited I am not sure if I understand everyone’s position. That's why I will ask some (maybe stupid) questions: Do we want more contributions from people which are not part of the apache foundation? If "yes": What kind of options are possible? Do we prefer some of these options? Are there any benefits from one over the others? Are there any risks in any of these options? If "no": Why? Do we want more contributons from people which are part of the apache foundation? If "yes": How can we achieve this? Are there any benefits using github? If "yes": How can we compete using the existing apache infrastructure? How must we improve to live happy without github? How long does it take? Are there any risks using github? If "yes": Which kind of risk? Can we reduce risks in any way? Is there any conflict with apache guidlines/legal/... using github at all? personal note: If I have to vote, it would not be easy for me to come to a clear conclusion. As I understand martijn, this is an apache project and we should honour this as good as we can. I understand martin and the others as they hope that we can attract more people to contribute and to use wicket more and more. It would surprise me, if we can not achieve both. Michael
          Hide
          Martijn Dashorst added a comment -

          I've written some docs for the new site about contributing and getting support:

          http://dashorst.github.io/wicket-site/contribute
          http://dashorst.github.io/wicket-site/support

          I'm still not sure about the separation and the flow of the documents, for example I miss the patch.md part still in contribute/index.md suggestions to improve that are welcome. Now I have to get back to work...

          Show
          Martijn Dashorst added a comment - I've written some docs for the new site about contributing and getting support: http://dashorst.github.io/wicket-site/contribute http://dashorst.github.io/wicket-site/support I'm still not sure about the separation and the flow of the documents, for example I miss the patch.md part still in contribute/index.md suggestions to improve that are welcome. Now I have to get back to work...
          Hide
          Martijn Dashorst added a comment -

          Michael Mosmann: I have no issue with using github at all. It is the promotion of github that I find worrying. The homepage of any Apache project is prime real estate and we should not promote any commercial service above or equal to our own, even if they are a million times better.

          So: yes github is an important way to get contributions and new contributors. I want to be able to keep on using github. As long as github remains open and provides such a good service there's no reason to abandon its use. Even if Apache were to get a similar private service that is open to the public, I don't think we should abandon the option of github contributions (if only because of its inertia, and because it is already currently allowed).

          For me the use of github is not an issue for debate: we can use it, we should use it and we should document its use. We should encourage people to contribute regardless of venue: through PR's, JIRA, dev@, bitbucket, sourceforge, a fax sent to secretary@ (good luck OCR-ing that thing), etc.

          The goal is to attract more contributors for our project, not to attract more users for Github. It is all about the message.

          Show
          Martijn Dashorst added a comment - Michael Mosmann : I have no issue with using github at all. It is the promotion of github that I find worrying. The homepage of any Apache project is prime real estate and we should not promote any commercial service above or equal to our own, even if they are a million times better. So: yes github is an important way to get contributions and new contributors. I want to be able to keep on using github. As long as github remains open and provides such a good service there's no reason to abandon its use. Even if Apache were to get a similar private service that is open to the public, I don't think we should abandon the option of github contributions (if only because of its inertia, and because it is already currently allowed). For me the use of github is not an issue for debate: we can use it, we should use it and we should document its use. We should encourage people to contribute regardless of venue: through PR's, JIRA, dev@, bitbucket, sourceforge, a fax sent to secretary@ (good luck OCR-ing that thing), etc. The goal is to attract more contributors for our project, not to attract more users for Github. It is all about the message.
          Hide
          Andrea Del Bene added a comment -

          I see that there are no link in the header to quickstart page and friends page. Should we add them back?

          Show
          Andrea Del Bene added a comment - I see that there are no link in the header to quickstart page and friends page. Should we add them back?
          Hide
          Martijn Dashorst added a comment -

          I wanted to move the quick start to the download page, and the friends page to another, possibly an Apache page or download, contribute or support.

          Maybe contribute should be renamed to community?

          I don't want more links than the current 6. When you look at the site with a small device or small-ish screen there is not enough room. The front page currently has the menu centred and room to spare, but the sub pages have the logo on the left and the menu on the right, limiting the amount of horizontal space available (in exchange for more vertical content room)

          Show
          Martijn Dashorst added a comment - I wanted to move the quick start to the download page, and the friends page to another, possibly an Apache page or download, contribute or support. Maybe contribute should be renamed to community? I don't want more links than the current 6. When you look at the site with a small device or small-ish screen there is not enough room. The front page currently has the menu centred and room to spare, but the sub pages have the logo on the left and the menu on the right, limiting the amount of horizontal space available (in exchange for more vertical content room)
          Hide
          Martijn Dashorst added a comment -

          Front page responsive design explained with examples for small, medium and large screens. A different design is in the works for non-frontpage content.

          Show
          Martijn Dashorst added a comment - Front page responsive design explained with examples for small, medium and large screens. A different design is in the works for non-frontpage content.
          Hide
          Martijn Dashorst added a comment -

          note that in image 6 the "elevator pitch" should be center-aligned, not left-aligned.

          Show
          Martijn Dashorst added a comment - note that in image 6 the "elevator pitch" should be center-aligned, not left-aligned.
          Hide
          Andrea Del Bene added a comment -

          I wanted to move the quick start to the download page, and the friends page to another, possibly an Apache page or download, contribute or support.

          Maybe contribute should be renamed to community?

          Good idea. I agree to rename it to community

          I don't want more links than the current 6. When you look at the site with a small device or small-ish screen there is not enough room. The front page currently has the menu centred and room to spare, but the sub pages have the logo on the left and the menu on the right, limiting the amount of horizontal space available (in exchange for more vertical content room)

          I see the point. But IMHO it would be good to keep a link to "quickstart" because we use to refer to it quite often in the user mailing list and so it would be nice to keep a direct link to it.

          How about the carousel? I saw you created a buildwithwicket page that (I guess) should contain the carousel. Are you planning to use some external library to implement the carousel?

          Show
          Andrea Del Bene added a comment - I wanted to move the quick start to the download page, and the friends page to another, possibly an Apache page or download, contribute or support. Maybe contribute should be renamed to community? Good idea. I agree to rename it to community I don't want more links than the current 6. When you look at the site with a small device or small-ish screen there is not enough room. The front page currently has the menu centred and room to spare, but the sub pages have the logo on the left and the menu on the right, limiting the amount of horizontal space available (in exchange for more vertical content room) I see the point. But IMHO it would be good to keep a link to "quickstart" because we use to refer to it quite often in the user mailing list and so it would be nice to keep a direct link to it. How about the carousel? I saw you created a buildwithwicket page that (I guess) should contain the carousel. Are you planning to use some external library to implement the carousel?
          Hide
          Chris Colman added a comment - - edited

          There are some styling/look and feel (whatever the graphic artists call it) issues that I thought might be worth raising. Hopefully this can be taken as constructive - I'm not trying to be negative.

          I fully appreciate the effect of the black and white photo on the home page instilling the idea of history and the stability that only comes from software with a long heritage but I think there are two potential issues with this:
          1. Once you click on any link on the home page the subsequent pages, with their modern blue banner and lack of black and white imagery, have a completely different look and feel compared to the home page - to me it feels like I have just moved to a totally different website. The blue banner feature of every other page has no visual association with the front page so there is no visual clue that I'm actually on the same website with the same styling.
          2. Black and white images are associated with a long, authentic, trusted history which is great but they are also associated with 'old' which may not be so great for newcomers to the site.

          I do like the idea of the image because it gives a human feel and a sense of the giants who have written this awesome framework and on whose shoulders we stand.

          Some possible solutions to the issues (at least I see them as issues IMHO, others may disagree) could be:

          Issue 1. Perhaps create a blue banner (same blue as on other pages) at the top - probably encompassing the main menu items and just high enough to encompass them. It shouldn't be as high as it is on the other pages because that would over power the image. By having this blue element on the home page we will be providing some visual consistency between the home page and the other pages and that would solve issue 1.

          Issue 2. What does it look like if the image of the original devs is color instead of black and white? Hopefully it can look modern but still show community and heritage. I think the first three words of the introduction "Invented in 2004" can capture the 'heritage' part quite well on it's own without needing the image to be black and white.

          Show
          Chris Colman added a comment - - edited There are some styling/look and feel (whatever the graphic artists call it) issues that I thought might be worth raising. Hopefully this can be taken as constructive - I'm not trying to be negative. I fully appreciate the effect of the black and white photo on the home page instilling the idea of history and the stability that only comes from software with a long heritage but I think there are two potential issues with this: 1. Once you click on any link on the home page the subsequent pages, with their modern blue banner and lack of black and white imagery, have a completely different look and feel compared to the home page - to me it feels like I have just moved to a totally different website. The blue banner feature of every other page has no visual association with the front page so there is no visual clue that I'm actually on the same website with the same styling. 2. Black and white images are associated with a long, authentic, trusted history which is great but they are also associated with 'old' which may not be so great for newcomers to the site. I do like the idea of the image because it gives a human feel and a sense of the giants who have written this awesome framework and on whose shoulders we stand. Some possible solutions to the issues (at least I see them as issues IMHO, others may disagree) could be: Issue 1. Perhaps create a blue banner (same blue as on other pages) at the top - probably encompassing the main menu items and just high enough to encompass them. It shouldn't be as high as it is on the other pages because that would over power the image. By having this blue element on the home page we will be providing some visual consistency between the home page and the other pages and that would solve issue 1. Issue 2. What does it look like if the image of the original devs is color instead of black and white? Hopefully it can look modern but still show community and heritage. I think the first three words of the introduction "Invented in 2004" can capture the 'heritage' part quite well on it's own without needing the image to be black and white.
          Hide
          Martijn Dashorst added a comment -

          Thanks for your comments.

          Issue 1 is quite easily resolved: the templates/styling are not finished yet. The idea is to have the image be on all pages, including the subpages, with the same height as the current blue ones.

          Issue 2 is difficult to address: the original images are not of good quality (2004 point and shoot digital camera, in low-light and in the winter (the attire is not quite fashionable). The colors are quite awful and really don't make the site look better. Also having a color image in the header makes it harder to match colors in the page.

          I'd also like to make the backgrounds switch between a couple of images from our community events. So on one page view you have one image, on the next refresh you get another (at random). Maybe even timed (switch once every minute) live in the page with css transitions. With multiple images it is even more difficult to match the colors to make the site look consistent.

          Show
          Martijn Dashorst added a comment - Thanks for your comments. Issue 1 is quite easily resolved: the templates/styling are not finished yet. The idea is to have the image be on all pages, including the subpages, with the same height as the current blue ones. Issue 2 is difficult to address: the original images are not of good quality (2004 point and shoot digital camera, in low-light and in the winter (the attire is not quite fashionable). The colors are quite awful and really don't make the site look better. Also having a color image in the header makes it harder to match colors in the page. I'd also like to make the backgrounds switch between a couple of images from our community events. So on one page view you have one image, on the next refresh you get another (at random). Maybe even timed (switch once every minute) live in the page with css transitions. With multiple images it is even more difficult to match the colors to make the site look consistent.
          Hide
          Martijn Dashorst added a comment -

          Added examples of sub-section pages in small, medium and wide responsive formats

          Show
          Martijn Dashorst added a comment - Added examples of sub-section pages in small, medium and wide responsive formats
          Hide
          Martijn Dashorst added a comment -

          I've fixed many small issues, revamped the templates to follow a logical structure, updated the top level menu for sub sections and auto-generated table of contents on the live site:

          http://dashorst.github.io/wicket-site/

          I think it is starting to look like something nice...

          Show
          Martijn Dashorst added a comment - I've fixed many small issues, revamped the templates to follow a logical structure, updated the top level menu for sub sections and auto-generated table of contents on the live site: http://dashorst.github.io/wicket-site/ I think it is starting to look like something nice...
          Hide
          Andrea Del Bene added a comment -

          I've fixed many small issues, revamped the templates to follow a logical structure, updated the top level menu for sub sections and auto-generated table of contents on the live site:

          http://dashorst.github.io/wicket-site/

          I think it is starting to look like something nice...

          Yes indeed . There is just a small issue I've noticed on the homepage. Class l-full is not applied on small devices (min-width: 590px) and this makes pictures to be displayed at full size.

          Show
          Andrea Del Bene added a comment - I've fixed many small issues, revamped the templates to follow a logical structure, updated the top level menu for sub sections and auto-generated table of contents on the live site: http://dashorst.github.io/wicket-site/ I think it is starting to look like something nice... Yes indeed . There is just a small issue I've noticed on the homepage. Class l-full is not applied on small devices (min-width: 590px) and this makes pictures to be displayed at full size.
          Hide
          Tobias Soloschenko added a comment -

          Cool new design - you could use my responsive image implementation to only load images in the required size - just kidding - hope to see it live, soon!

          Show
          Tobias Soloschenko added a comment - Cool new design - you could use my responsive image implementation to only load images in the required size - just kidding - hope to see it live, soon!
          Hide
          Tobias Soloschenko added a comment -

          I had a look at the new design with a mobile device. (resolution: 1136 x 640) The images are bigger then the horizontal view port, so they are breaking the layout.

          Show
          Tobias Soloschenko added a comment - I had a look at the new design with a mobile device. (resolution: 1136 x 640) The images are bigger then the horizontal view port, so they are breaking the layout.
          Hide
          Martijn Dashorst added a comment -

          Which images are you referring to? The logo, the background or the front page images in "Introducing Apache Wicket"?

          Show
          Martijn Dashorst added a comment - Which images are you referring to? The logo, the background or the front page images in "Introducing Apache Wicket"?
          Hide
          Andrea Del Bene added a comment -

          the images in "Introducing Apache Wicket". Class l-full is not applied on small devices (min-width: 590px) and this makes pictures to be displayed at full size.

          Show
          Andrea Del Bene added a comment - the images in "Introducing Apache Wicket". Class l-full is not applied on small devices (min-width: 590px) and this makes pictures to be displayed at full size.
          Hide
          Tobias Soloschenko added a comment -

          Ah, I didn't know what you meant by "small devices", but yes I can confirm this issue.

          Show
          Tobias Soloschenko added a comment - Ah, I didn't know what you meant by "small devices", but yes I can confirm this issue.
          Hide
          Andrea Del Bene added a comment -
          Show
          Andrea Del Bene added a comment - The fresh-new quickstart page: http://bitstorm.github.io/wicket-site/start/quickstart.html
          Hide
          Martijn Dashorst added a comment -

          Fixed this issue by applying width:100% on l-full when device resolution is "small". You should be able to see it fixed on http://dashorst.github.io/wicket-site

          Show
          Martijn Dashorst added a comment - Fixed this issue by applying width:100% on l-full when device resolution is "small". You should be able to see it fixed on http://dashorst.github.io/wicket-site
          Hide
          Martijn Dashorst added a comment -

          Thx! I've merged your commits to my repository.

          Show
          Martijn Dashorst added a comment - Thx! I've merged your commits to my repository.
          Hide
          Martijn Dashorst added a comment -

          Thx! I've merged your commits to my repository.

          Show
          Martijn Dashorst added a comment - Thx! I've merged your commits to my repository.
          Hide
          Tobias Soloschenko added a comment -

          Yep the fix works for me. Looks good, now.

          Show
          Tobias Soloschenko added a comment - Yep the fix works for me. Looks good, now.
          Hide
          Martijn Dashorst added a comment -

          I've updated the test site with the carroussel (taken from and worked on further the awesome work by Andrea, it was just a pain to get it to work properly), edited the content of several pages (including pages that are empty on our current site) and added some buttons for flair.

          The button bar is not fully responsive so that will take a little work to get right. Also the caption in the button should start at the bottom of the button for alignment.

          See for yourself:

          Show
          Martijn Dashorst added a comment - I've updated the test site with the carroussel (taken from and worked on further the awesome work by Andrea, it was just a pain to get it to work properly), edited the content of several pages (including pages that are empty on our current site) and added some buttons for flair. The button bar is not fully responsive so that will take a little work to get right. Also the caption in the button should start at the bottom of the button for alignment. See for yourself: Carroussel: http://dashorst.github.io/wicket-site Button bar: http://dashorst.github.io/wicket-site/help/
          Hide
          Andrea Del Bene added a comment -

          Great looking as usual . I've opened a pull request to fix a typo for page patch.html and to improve the layout for userguide.html.

          Show
          Andrea Del Bene added a comment - Great looking as usual . I've opened a pull request to fix a typo for page patch.html and to improve the layout for userguide.html.
          Hide
          Chris Colman added a comment - - edited

          I've built a list of links on the existing site - about 8000!

          About 99% of these are URLs beginning with:

          http://wicket.apache.org/apidocs/1.5

          are we going to keep the 1.5 docs as part of the new website or do what was done with all the other API docs i.e. hosted under a different subdomain:

          eg.
          http://ci.apache.org/projects/wicket/apidocs/6.x/

          We should probably just add a permanent redirect like
          http://wicket.apache.org/apidocs/1.5/* => http://ci.apache.org/projects/wicket/apidocs/1.5.x/

          so that any link to the old 1.5 apidoc pages is linked to home page of 1.5 doc on the ci.apache.org subdomain.

          Extraction of all existing links is in attachment of Subtask 5.

          I've been asked to do a presentation on Wicket at a client's premises and thought it would be nice that when I give them the wicket URL it takes them to the new sexy website.

          Show
          Chris Colman added a comment - - edited I've built a list of links on the existing site - about 8000! About 99% of these are URLs beginning with: http://wicket.apache.org/apidocs/1.5 are we going to keep the 1.5 docs as part of the new website or do what was done with all the other API docs i.e. hosted under a different subdomain: eg. http://ci.apache.org/projects/wicket/apidocs/6.x/ We should probably just add a permanent redirect like http://wicket.apache.org/apidocs/1.5/* => http://ci.apache.org/projects/wicket/apidocs/1.5.x/ so that any link to the old 1.5 apidoc pages is linked to home page of 1.5 doc on the ci.apache.org subdomain. Extraction of all existing links is in attachment of Subtask 5. I've been asked to do a presentation on Wicket at a client's premises and thought it would be nice that when I give them the wicket URL it takes them to the new sexy website.
          Hide
          Martin Grigorov added a comment -

          I'd suggest to keep the old link. No need to make it prettier (1.5.x) and this way there won't be need to reconfigure BuildBot (our CI server).

          Show
          Martin Grigorov added a comment - I'd suggest to keep the old link. No need to make it prettier (1.5.x) and this way there won't be need to reconfigure BuildBot (our CI server).
          Hide
          Chris Colman added a comment -

          By "old link" do you mean the thousands of apidoc "linkS"? So we just leave those apidoc pages where they are when updating the website? That should work. It just means that when we update the site with the new pages we can't do a

          rm -r *

          on the root directory of the website - rather will have to copy the new pages into it.

          Show
          Chris Colman added a comment - By "old link" do you mean the thousands of apidoc "linkS"? So we just leave those apidoc pages where they are when updating the website? That should work. It just means that when we update the site with the new pages we can't do a rm -r * on the root directory of the website - rather will have to copy the new pages into it.
          Hide
          Martin Grigorov added a comment -

          Hm.
          Looking at the site (http://wicket.apache.org/) I see a link to http://ci.apache.org/projects/wicket/apidocs/1.5.x/.

          I see that http://wicket.apache.org/apidocs/1.5 is a valid url, but I have no idea where the site links to it. I guess these javadocs are very outdated.

          Show
          Martin Grigorov added a comment - Hm. Looking at the site ( http://wicket.apache.org/ ) I see a link to http://ci.apache.org/projects/wicket/apidocs/1.5.x/ . I see that http://wicket.apache.org/apidocs/1.5 is a valid url, but I have no idea where the site links to it. I guess these javadocs are very outdated.
          Hide
          Martin Grigorov added a comment -

          The new site has been deployed with Wicket 7.0.0 release!
          If any issues are found with it please create new issue.

          Show
          Martin Grigorov added a comment - The new site has been deployed with Wicket 7.0.0 release! If any issues are found with it please create new issue.

            People

            • Assignee:
              Martijn Dashorst
              Reporter:
              Martijn Dashorst
            • Votes:
              4 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development