Hi Justin, First of all, the new website looks much better then the current one - it has much more modern and elegant look. It will definitely leave a lot better first impression on new visitors :-). Thanks for the good job. But I still have some points which can be IMHO improved (from my personal view) ...
On the front page, the main space looks nice and gives a quick overview. But the right column seems to me a bit chaotic. The ">>-Developers!->" button looks strange due to the different font and the use of special characters. The Apache links above the button look ok, but is there some reason why they are in the right column on the front page and at the bottom on every other page? Wouldn't it be better to have it consistent across all pages? The "Resources" section kind of mirrors the menu on the top, but it has slightly different structure. On the top menu you use the "Resources" button to link to the page with links to blogs etc. But in the right column, this is named "More" and you use "Resources" as a name for the subsection. And then there are the sections "Qpid" and "Qpid Proton" in the right column. The "Qpid" contains only some links while the "Qpid Proton" contains an explanation what Proton is. I would probably add some similar explanation to the Qpid as well. It kind of makes me feel that Qpid is only the project name and Qpid Proton is the actual product name. Also, is there some reason why the background on the front page is different from the other pages? Fully white on the front page versus the coloured frame on the rest of the pages? What I'm missing on the front page is some quick access to the documentation as was on the old site. Now you have to go to components, select the component and only then you can get the documentation. I think it would deserve a faster access. I also didn't found any way how to get to the trunk documentation - is there some link I missed or is it not planned to have one? It would be also great to have the search button more highlighted - it is a bit lost right now in the upper right corner. And having some search input field immediately on the site without needing to go to the search page first would be nice as well :-). I have also one technical comment ... the site is often moving few pixels left or right when moving from page to page. It is not a big issue, but it doesn't look nice. It happens for example if I click between "Download" and "Components". (Chrome 26.0.1410.43 on Windows 7) Thanks & Regards Jakub On Thu, Apr 4, 2013 at 1:12 AM, Justin Ross <[email protected]> wrote: > Update: > http://people.apache.org/~jross/transom/2013-04-03/ > Previous version: > http://people.apache.org/~jross/transom/2013-03-26/ > Head version (if you want to follow things as they change): > http://people.apache.org/~jross/transom/head/ > The source code: > https://github.com/ssorj/transom > > I have a feeling the most noticed change will be the page width. It's > now set to a max width just a hair wider (leftmost to rightmost > character) than our current site. In addition, it scales down to fit > comfortably in one half of a wide desktop display or a mobile device > in portrait. > > There remain plenty of things to do: > https://github.com/ssorj/transom/blob/master/TODO. Check there to see > if the thing you'd like to have is still incoming. > > Topics for discussion: > - Should we rename AMQP Messenger (and its buddy) to Proton > Messenger to clarify the link to the toolkit? > - Alternatively, should we give up on treating messenger and > protocol engine as peers to jms and the messaging api, etc., and just > call it the "Proton component"? > - Is "Component" a terrible name for an end-user-facing, > independently usable, independently documented Qpid subunit? Do you > have suggestions? > > Changes: > - Content: > - Many of operational links on the right have been "bubbled down", > simplifiying the right side of the front page > - I intend to restore some of these under the currently > stubbed-out developer page > - Avoid personal pronoun in project statement > - Employ Rafi's language for user scenarios in the intro text > - Make download the primary entry point for qpid release content > - Add site, wiki, and jira search under a consolidated search interface > - Make it clear from the messenger and protocol engine component > pages that they are part of proton > - Retarget download links in previous releases at archive.apache.org > - Add or clarify trademarks > - The big title still needs one; it's blocked on an xml/unicode > problem > - Under components > - Use "servers" instead of "brokers" > - Add a tool section, and move QMF there > - Add a JCA component, also under tools > - Note in JMS component that 1.0 is a separate artifact from the > other versions > - Under download > - Restore the AMQP prefix to proton components > - Note that some artifacts are bytecode, and link to source > - Move the verification text and more-ways-to-get-qpid link here > - Navigation > - Add persistent top nav > - Path navigation is displayed only when you're deep in the tree > and need it to know where you are > - Promoted apache links on the front page to the right hand column > - Many style tweaks > > Thanks! > Justin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
