[
https://issues.apache.org/jira/browse/BEAM-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652712#comment-16652712
]
Melissa Pashniak edited comment on BEAM-5741 at 10/17/18 12:15 AM:
-------------------------------------------------------------------
Would this be an addition section, or replace the Community section? I don't
really agree with adding yet another item, there are two aspects here:
1) We have done a lot of rearranging of the navigation on the site, and as part
of this, we looked at many sites when we landed on our current breakdown. On a
majority of the sites that use a top nav structure, the contact us/mailing list
pages are in a nav item "Community" (for example many Apache sites - Spark,
Apex, Hadoop, Gearpump, and other big projects such as Tensorflow, Kubernetes,
etc.) Because of this, we used the same "Community" terminology for
consistency, and made the contact us page the default page that shows up when
someone chooses Community. We used to have pull-down menus on the top nav, but
we received feedback that it caused trouble for mobile devices because the
menus were too long. We could attempt to put that back and only have a small
subset of options, though it might be confusing to show some things but not all
unless they click on the item. We could also move to a permanent static left
nav structure to show more items at once (such as Flink, which has a "Getting
help" page that is always visible), but then we'd lose the section-specific
left nav when you choose a top nav item.
2) The other issue is one of remaining horizontal space. I am looking into
adding searching capability/a search bar for the site, which would take up a
big chunk of the remaining space after the top nav items. we are already
nearing (imo) too many top level nav items. (some actually weren't enthused
with how many are there even now)
was (Author: melap):
Would this replace the Community section? I don't really agree with this, there
are two aspects here:
1) We have done a lot of rearranging of the navigation on the site, and as part
of this, we looked at many sites when we landed on our current breakdown. On a
majority of the sites that use a top nav structure, the contact us/mailing list
pages are in a nav item "Community" (for example many Apache sites - Spark,
Apex, Hadoop, Gearpump, and other big projects such as Tensorflow, Kubernetes,
etc.) Because of this, we used the same "Community" terminology for
consistency, and made the contact us page the default page that shows up when
someone chooses Community. We used to have pull-down menus on the top nav, but
we received feedback that it caused trouble for mobile devices because the
menus were too long. We could attempt to put that back and only have a small
subset of options, though it might be confusing to show some things but not all
unless they click on the item. We could also move to a permanent static left
nav structure to show more items at once (such as Flink, which has a "Getting
help" page that is always visible), but then we'd lose the section-specific
left nav when you choose a top nav item.
2) The other issue is one of remaining horizontal space. I am looking into
adding searching capability/a search bar for the site, which would take up a
big chunk of the remaining space after the top nav items. we are already
nearing (imo) too many top level nav items. (some actually weren't enthused
with how many are there even now)
> Move "Contact Us" to a top-level link
> -------------------------------------
>
> Key: BEAM-5741
> URL: https://issues.apache.org/jira/browse/BEAM-5741
> Project: Beam
> Issue Type: Sub-task
> Components: website
> Reporter: Scott Wegner
> Priority: Major
>
> It should be very easy to figure out how to get in touch with community.
> "Contact Us" should be a top-level link on the page.
> The page can also be improved with:
> * Some basic text on how to use subscribe / unsubscribe links
> * Recommendations on how to use various communications channels (Slack for
> quick questions, dev@ for longer conversations. And all decisions should make
> it back to dev@)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
