You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Justin Ross <jr...@apache.org> on 2013/04/04 01:12:31 UTC
Website update 2
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: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Website update 2
Posted by Jakub Scholz <ja...@scholz.cz>.
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 <jr...@apache.org> 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: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Website update 2
Posted by Robbie Gemmell <ro...@gmail.com>.
On 5 April 2013 16:43, Justin Ross <jr...@apache.org> wrote:
> Hi, Alex. Thanks for the comments.
>
> On Thu, Apr 4, 2013 at 6:57 PM, Oleksandr Rudyy <or...@gmail.com> wrote:
> > Hi Justin,
> >
> > The new version looks really nice. Well done.
> > However, I got a couple of minor comments.
> >
> > General remarks:
> >
> > I do not know if it is me (may be I am getting older and more
> conservative
> > :) ) but I would decrease slightly the size of the fonts. They look
> bigger
> > than I get used to.
>
> I agree. While I think modern websites do make the fonts a little
> bigger, this still a little bigger than I prefer. I have competing
> concern, however.
>
> http://people.apache.org/~jross/transom/narrow.png
> http://people.apache.org/~jross/transom/wide.png
>
> In both of these renderings, I've reduced the font to the size I like
> better. In the wide layout, it produces a big gap in the middle that
> I think looks bad. That's why I bumped the font size up a little in
> the current version. If the wider layout with the smaller font works
> for you, I can go back to that.
>
> > Front page.
> >
> > I would like to suggest to remove couple of redundancies which appeared
> in
> > the new version of the site:
> > - The download button in the right top corner seems like does not bring
> > anything new as there is already download link in the top menu.
>
> In this case, I think the redundancy may be justified. The download
> operation is high priority, one of the main things folks coming to our
> site want to do. That's why I consider it justified.
>
>
I dont mind there being an additional 'high visibility' download link, but
something about the way it is now also doesn't sit that well with me.
Download Now, perhaps? Maybe a slightly different colour from the rest of
the content to make it stick out more?
> - The phrase "Qpid is an Apache <http://www.apache.org/> project" seems
> > like another duplication as the title of the site does not leave any
> place
> > for doubts that it is not an Apache project. Maybe it can be replaced
> with
> > the link to AMQP site? I would move the link to Apache main web site into
> > Apache sub-section below.
>
> Okay. I like it there because that block is a concise statement of
> our project. But of course, you're right, there's no shyness about
> the Apache connection.
>
>
I remember adding that kind of statement on the existing site, im fairly
sure the project branding guidelines say it should have something to that
effect.
> > Also, I would improve the Developers link. It looks like an incorrectly
> > written html comment for me. I would make it similar to the sections
> above
> > ("Apache", "Resources", "Qpid Proton" etc.) and put some links
> underneath,
> > for example, link to road map page (if we are going to maintain it
> > accurately), qpid_project_etiquette_guide.html, code styles?, etc.
>
> I'll work on a different approach. At this point, I don't want to
> promote project etiquette and that kind of thing to the front page.
> I'm planning to instead link that stuff off the developer home.
>
> > I got a question about documentation for previous releases. There are
> > links to the current documentation on each component page. But what about
> > the links to the documentation for previous releases? Have I missed it?
>
> In the new site, all the version-specific documentation is collected
> under its corresponding release. For example,
>
>
> http://people.apache.org/~jross/transom/head/releases/qpid-0.20/index.html
>
> http://people.apache.org/~jross/transom/head/releases/qpid-0.20/messaging-api/cpp/api/index.html
>
> (Note that I haven't regenerated all the docs for releases before 0.20.)
>
> There is a link to the release index at the bottom of the download
> page. I'm at adding in addition some text at the top of the download
> page pointing to previous releases, and your comment here has started
> me thinking about how to do it under the component pages.
>
Yeah, I also found it rather difficult to locate the prior version
documentation (and indeed the prior releases arent that easy to find) if
you dont already know where they were.
>
> Thanks,
> Justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Website update 2
Posted by Oleksandr Rudyy <or...@gmail.com>.
Hi Justin,
Thanks for making the versions of the site with smaller fonts.
I really like the wider version. It looks all right for me even with the
spaces.
Kind Regards,
Alex
On 5 April 2013 16:43, Justin Ross <jr...@apache.org> wrote:
> Hi, Alex. Thanks for the comments.
>
> On Thu, Apr 4, 2013 at 6:57 PM, Oleksandr Rudyy <or...@gmail.com> wrote:
> > Hi Justin,
> >
> > The new version looks really nice. Well done.
> > However, I got a couple of minor comments.
> >
> > General remarks:
> >
> > I do not know if it is me (may be I am getting older and more
> conservative
> > :) ) but I would decrease slightly the size of the fonts. They look
> bigger
> > than I get used to.
>
> I agree. While I think modern websites do make the fonts a little
> bigger, this still a little bigger than I prefer. I have competing
> concern, however.
>
> http://people.apache.org/~jross/transom/narrow.png
> http://people.apache.org/~jross/transom/wide.png
>
> In both of these renderings, I've reduced the font to the size I like
> better. In the wide layout, it produces a big gap in the middle that
> I think looks bad. That's why I bumped the font size up a little in
> the current version. If the wider layout with the smaller font works
> for you, I can go back to that.
>
> > Front page.
> >
> > I would like to suggest to remove couple of redundancies which appeared
> in
> > the new version of the site:
> > - The download button in the right top corner seems like does not bring
> > anything new as there is already download link in the top menu.
>
> In this case, I think the redundancy may be justified. The download
> operation is high priority, one of the main things folks coming to our
> site want to do. That's why I consider it justified.
>
> > - The phrase "Qpid is an Apache <http://www.apache.org/> project" seems
> > like another duplication as the title of the site does not leave any
> place
> > for doubts that it is not an Apache project. Maybe it can be replaced
> with
> > the link to AMQP site? I would move the link to Apache main web site into
> > Apache sub-section below.
>
> Okay. I like it there because that block is a concise statement of
> our project. But of course, you're right, there's no shyness about
> the Apache connection.
>
> > Also, I would improve the Developers link. It looks like an incorrectly
> > written html comment for me. I would make it similar to the sections
> above
> > ("Apache", "Resources", "Qpid Proton" etc.) and put some links
> underneath,
> > for example, link to road map page (if we are going to maintain it
> > accurately), qpid_project_etiquette_guide.html, code styles?, etc.
>
> I'll work on a different approach. At this point, I don't want to
> promote project etiquette and that kind of thing to the front page.
> I'm planning to instead link that stuff off the developer home.
>
> > I got a question about documentation for previous releases. There are
> > links to the current documentation on each component page. But what about
> > the links to the documentation for previous releases? Have I missed it?
>
> In the new site, all the version-specific documentation is collected
> under its corresponding release. For example,
>
>
> http://people.apache.org/~jross/transom/head/releases/qpid-0.20/index.html
>
> http://people.apache.org/~jross/transom/head/releases/qpid-0.20/messaging-api/cpp/api/index.html
>
> (Note that I haven't regenerated all the docs for releases before 0.20.)
>
> There is a link to the release index at the bottom of the download
> page. I'm at adding in addition some text at the top of the download
> page pointing to previous releases, and your comment here has started
> me thinking about how to do it under the component pages.
>
> Thanks,
> Justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Website update 2
Posted by Justin Ross <jr...@apache.org>.
Hi, Alex. Thanks for the comments.
On Thu, Apr 4, 2013 at 6:57 PM, Oleksandr Rudyy <or...@gmail.com> wrote:
> Hi Justin,
>
> The new version looks really nice. Well done.
> However, I got a couple of minor comments.
>
> General remarks:
>
> I do not know if it is me (may be I am getting older and more conservative
> :) ) but I would decrease slightly the size of the fonts. They look bigger
> than I get used to.
I agree. While I think modern websites do make the fonts a little
bigger, this still a little bigger than I prefer. I have competing
concern, however.
http://people.apache.org/~jross/transom/narrow.png
http://people.apache.org/~jross/transom/wide.png
In both of these renderings, I've reduced the font to the size I like
better. In the wide layout, it produces a big gap in the middle that
I think looks bad. That's why I bumped the font size up a little in
the current version. If the wider layout with the smaller font works
for you, I can go back to that.
> Front page.
>
> I would like to suggest to remove couple of redundancies which appeared in
> the new version of the site:
> - The download button in the right top corner seems like does not bring
> anything new as there is already download link in the top menu.
In this case, I think the redundancy may be justified. The download
operation is high priority, one of the main things folks coming to our
site want to do. That's why I consider it justified.
> - The phrase "Qpid is an Apache <http://www.apache.org/> project" seems
> like another duplication as the title of the site does not leave any place
> for doubts that it is not an Apache project. Maybe it can be replaced with
> the link to AMQP site? I would move the link to Apache main web site into
> Apache sub-section below.
Okay. I like it there because that block is a concise statement of
our project. But of course, you're right, there's no shyness about
the Apache connection.
> Also, I would improve the Developers link. It looks like an incorrectly
> written html comment for me. I would make it similar to the sections above
> ("Apache", "Resources", "Qpid Proton" etc.) and put some links underneath,
> for example, link to road map page (if we are going to maintain it
> accurately), qpid_project_etiquette_guide.html, code styles?, etc.
I'll work on a different approach. At this point, I don't want to
promote project etiquette and that kind of thing to the front page.
I'm planning to instead link that stuff off the developer home.
> I got a question about documentation for previous releases. There are
> links to the current documentation on each component page. But what about
> the links to the documentation for previous releases? Have I missed it?
In the new site, all the version-specific documentation is collected
under its corresponding release. For example,
http://people.apache.org/~jross/transom/head/releases/qpid-0.20/index.html
http://people.apache.org/~jross/transom/head/releases/qpid-0.20/messaging-api/cpp/api/index.html
(Note that I haven't regenerated all the docs for releases before 0.20.)
There is a link to the release index at the bottom of the download
page. I'm at adding in addition some text at the top of the download
page pointing to previous releases, and your comment here has started
me thinking about how to do it under the component pages.
Thanks,
Justin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Website update 2
Posted by Oleksandr Rudyy <or...@gmail.com>.
Hi Justin,
The new version looks really nice. Well done.
However, I got a couple of minor comments.
General remarks:
I do not know if it is me (may be I am getting older and more conservative
:) ) but I would decrease slightly the size of the fonts. They look bigger
than I get used to.
Front page.
I would like to suggest to remove couple of redundancies which appeared in
the new version of the site:
- The download button in the right top corner seems like does not bring
anything new as there is already download link in the top menu.
- The phrase "Qpid is an Apache <http://www.apache.org/> project" seems
like another duplication as the title of the site does not leave any place
for doubts that it is not an Apache project. Maybe it can be replaced with
the link to AMQP site? I would move the link to Apache main web site into
Apache sub-section below.
Also, I would improve the Developers link. It looks like an incorrectly
written html comment for me. I would make it similar to the sections above
("Apache", "Resources", "Qpid Proton" etc.) and put some links underneath,
for example, link to road map page (if we are going to maintain it
accurately), qpid_project_etiquette_guide.html, code styles?, etc.
I got a question about documentation for previous releases. There are
links to the current documentation on each component page. But what about
the links to the documentation for previous releases? Have I missed it?
Kind Regards,
Alex
On 4 April 2013 00:12, Justin Ross <jr...@apache.org> 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: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Website update 2
Posted by Rob Godfrey <ro...@gmail.com>.
On 7 April 2013 21:03, Robbie Gemmell <ro...@gmail.com> wrote:
> On 4 April 2013 00:12, Justin Ross <jr...@apache.org> 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.
> >
> >
> Much better :)
>
> I also agree with Alex about the font perhaps being a smidge large, when
> viewing on desktops at least.
>
>
> > 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?
> >
>
> I think that would be clearer, to me at least (if not just Messenger). We
> don't call it AMQP Messenger anywhere else, and doing so seems to makes it
> unclear that its part of Proton.
>
>
>
So - I kind of disagree here... One of the things I think we should really
be trying to convey is that we are producing AMQP clients. If people are
searching for an AMQP API I want our work to be easily found. The fact
that Messenger is part of the Proton component within the Qpid project
doesn't really seem like the most important piece of information to
convey.
-- Rob
> - 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
> >
>
> The 'java release' is actually not source but another binary, just a really
> really horrible super set of the other binary release packages (amongest
> other thigns that dont have release packags). Someting that I really need
> to follow through on my intent to delete.
>
> The only copy of the Java source is in the 'full release' source archive.
>
>
> > - 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: users-unsubscribe@qpid.apache.org
> > For additional commands, e-mail: users-help@qpid.apache.org
> >
> >
>
Re: Website update 2
Posted by Robbie Gemmell <ro...@gmail.com>.
On 4 April 2013 00:12, Justin Ross <jr...@apache.org> 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.
>
>
Much better :)
I also agree with Alex about the font perhaps being a smidge large, when
viewing on desktops at least.
> 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?
>
I think that would be clearer, to me at least (if not just Messenger). We
don't call it AMQP Messenger anywhere else, and doing so seems to makes it
unclear that its part of Proton.
> - 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
>
The 'java release' is actually not source but another binary, just a really
really horrible super set of the other binary release packages (amongest
other thigns that dont have release packags). Someting that I really need
to follow through on my intent to delete.
The only copy of the Java source is in the 'full release' source archive.
> - 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: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Website update 2
Posted by Rafael Schloming <rh...@alum.mit.edu>.
On Wed, Apr 3, 2013 at 7:12 PM, Justin Ross <jr...@apache.org> 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?
>
The way I think of it is that "Messenger" is the name of the API, and "AMQP
Messenger" is the implementation of the API that speaks AMQP, and that is
all part of Proton. I'm not suggesting we would necessarily ever bother
extending the implementation to speak anything else, nor do I think of
Messenger as an API that we are seeking third party implementations for,
just observing that logically more than one set of terms makes sense. I
think defacto the name of Messenger is just Messenger as that is what
people are most likely to call it, and we need to make the relationship of
Messenger to both AMQP and Proton clear, and using terms like AMQP
Messenger and/or Proton Messenger could all be reasonable in the
appropriate context.
I don't know if the above helps much, but I think it's actually the
arrangement of the information that is losing a bit of the story on what
Proton actually is, and what is its relationship to Messenger. For example
Messenger is a part of Proton, yet it doesn't appear underneath Proton in
the hierarchy of the site. I guess to sum it up, Messenger and Engine are
presented as two independent top level things, whereas in the current site
they are presented as two parts of one thing (Proton). I would say we
probably want to steer a bit more towards the latter picture given the API
discussion on the list as I think when Messenger surfaces its transports in
order to allow custom drivers, they will really have evolved to the point
of being two different facets of the same thing.
FWIW, I very much like the way you have presented information on the top
level page, with the grey box calling out the "headline" for what qpid is
and then very relevant information presented below that with useful stuff
on the right hand side. I think a similar layout could work well on the
proton page where the "headline" would be Messenger with a more nuanced
picture presented below and some of the more mundane stuff (like the bug
box) over on the right. I think that general layout could make a very good
template for each of the independently releasable sub-units of Qpid.
- 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"?
>
I don't think it's bad to call out those APIs into a flattened list the way
you currently have. In fact I think it's good. I would just say that each
sub-unit of qpid might have multiple interesting facets that want to be
pulled out here, and we shouldn't lose the overall structure, i.e. we
shouldn't try to hide that there are really three levels here: qpid ->
sub-unit -> facet. Where by sub-unit I mean independently releasable chunk,
i.e. a single source artifact.
> - Is "Component" a terrible name for an end-user-facing,
> independently usable, independently documented Qpid subunit? Do you
> have suggestions?
>
Possibly, I tend to think of component as a more concrete unit, and some of
the things you are calling components are actually APIs, and APIs are of
course "Abstract". I think in the three level view of things you could
perhaps get away with it, e.g. Qpid -> Sub Project -> Component. You could
also consider using Component as the term for the second level, e.g. Qpid
-> Component -> ___, but that leaves you with no obvious name for that
third level of things. Facet seems too abstract, and feature seems too fine
grained. You could of course simply go with Qpid -> Component -> (API |
Tool | Utility | Server), i.e. expand out the third level into a more
concrete term and never reference the abstract category.
--Rafael