You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Melissa Pashniak <me...@google.com.INVALID> on 2017/10/16 21:23:14 UTC
[Proposal] Beam website navigation update
Hello Beam folks,
I've received some good feedback that the Beam website can be difficult to
navigate, due to such things as:
- The top pulldown menus are too long and you can't select things at the
end, and this will only get worse as we create more pages
- The programming guide as a single page is too long and difficult to
navigate
- Navigation issues on mobile devices
In order to tackle these issues, we (myself and David Perez) have put
together a staged proposal [1] for an improved navigation story. It
includes:
- A new left nav that contains the lists of items previously in the top
pulldown. It's easy to change what items are displayed, you can nest
arbitrary items, etc. The left nav is scrollable on small windows, so you
can always reach everything. Users can now jump between programming guide
sections easily.
- On the right is a list of the sections within a page, so you can quickly
jump to where you want. The list is autogenerated from the sections in the
page.
- Mobile improvements such as: you can now get to the top nav items from
the home page.
This PR [2] would just be the first step. Once merged, it opens up other
improvements:
- Break apart the major sections of the programming guide into separate
pages. This allows for the addition of more details and code samples for
each section, without making an already-too-large page even larger. With
the left nav, jumping between these pages will be easy.
- A proper overview landing page for the SDKs section, that lists the
available SDKs, any differences, etc.
- Tweaking left nav items to bubble up previously hard-to-find content (for
example, the Python type safety and Python dependencies pages)
Please check it out and see what you think -- we'd love to get your
feedback.
Thanks!
[1] http://apache-beam-website-pull-requests.storage.
googleapis.com/332/index.html
[2] https://github.com/apache/beam-site/pull/332
Re: [Proposal] Beam website navigation update
Posted by Hadar Hod <ha...@google.com.INVALID>.
Wow, Melissa, this looks great! Thanks for your hard work on this!
On Thu, Oct 19, 2017 at 12:24 PM, Griselda Cuevas <gr...@google.com.invalid>
wrote:
> +1
>
> This looks amazing Melissa! -- The left navigation gives more visibility on
> what documentation is available in the website and helps new users follow
> the flow. Also, the mobile experience looks better now. Thank you for the
> great work here.
>
>
> Gris Cuevas Zambrano
>
> gris@google.com
>
> Open Source Strategy
>
> 345 Spear Street, San Francisco, 94105
>
>
>
> On 17 October 2017 at 14:07, Kenneth Knowles <kl...@google.com.invalid>
> wrote:
>
> > This looks so good. Definitely makes the website more understandable, and
> > especially invites more documentation to be written!
> >
> > I'll try to have some more concrete feedback on the PR.
> >
> > Kenn
> >
> > On Mon, Oct 16, 2017 at 2:23 PM, Melissa Pashniak <
> > melissapa@google.com.invalid> wrote:
> >
> > > Hello Beam folks,
> > >
> > > I've received some good feedback that the Beam website can be difficult
> > to
> > > navigate, due to such things as:
> > >
> > > - The top pulldown menus are too long and you can't select things at
> the
> > > end, and this will only get worse as we create more pages
> > > - The programming guide as a single page is too long and difficult to
> > > navigate
> > > - Navigation issues on mobile devices
> > >
> > > In order to tackle these issues, we (myself and David Perez) have put
> > > together a staged proposal [1] for an improved navigation story. It
> > > includes:
> > >
> > > - A new left nav that contains the lists of items previously in the top
> > > pulldown. It's easy to change what items are displayed, you can nest
> > > arbitrary items, etc. The left nav is scrollable on small windows, so
> you
> > > can always reach everything. Users can now jump between programming
> guide
> > > sections easily.
> > > - On the right is a list of the sections within a page, so you can
> > quickly
> > > jump to where you want. The list is autogenerated from the sections in
> > the
> > > page.
> > > - Mobile improvements such as: you can now get to the top nav items
> from
> > > the home page.
> > >
> > > This PR [2] would just be the first step. Once merged, it opens up
> other
> > > improvements:
> > >
> > > - Break apart the major sections of the programming guide into separate
> > > pages. This allows for the addition of more details and code samples
> for
> > > each section, without making an already-too-large page even larger.
> With
> > > the left nav, jumping between these pages will be easy.
> > > - A proper overview landing page for the SDKs section, that lists the
> > > available SDKs, any differences, etc.
> > > - Tweaking left nav items to bubble up previously hard-to-find content
> > (for
> > > example, the Python type safety and Python dependencies pages)
> > >
> > > Please check it out and see what you think -- we'd love to get your
> > > feedback.
> > >
> > > Thanks!
> > >
> > > [1] http://apache-beam-website-pull-requests.storage.
> > > googleapis.com/332/index.html
> > > [2] https://github.com/apache/beam-site/pull/332
> > >
> >
>
Re: [Proposal] Beam website navigation update
Posted by Griselda Cuevas <gr...@google.com.INVALID>.
+1
This looks amazing Melissa! -- The left navigation gives more visibility on
what documentation is available in the website and helps new users follow
the flow. Also, the mobile experience looks better now. Thank you for the
great work here.
Gris Cuevas Zambrano
gris@google.com
Open Source Strategy
345 Spear Street, San Francisco, 94105
On 17 October 2017 at 14:07, Kenneth Knowles <kl...@google.com.invalid> wrote:
> This looks so good. Definitely makes the website more understandable, and
> especially invites more documentation to be written!
>
> I'll try to have some more concrete feedback on the PR.
>
> Kenn
>
> On Mon, Oct 16, 2017 at 2:23 PM, Melissa Pashniak <
> melissapa@google.com.invalid> wrote:
>
> > Hello Beam folks,
> >
> > I've received some good feedback that the Beam website can be difficult
> to
> > navigate, due to such things as:
> >
> > - The top pulldown menus are too long and you can't select things at the
> > end, and this will only get worse as we create more pages
> > - The programming guide as a single page is too long and difficult to
> > navigate
> > - Navigation issues on mobile devices
> >
> > In order to tackle these issues, we (myself and David Perez) have put
> > together a staged proposal [1] for an improved navigation story. It
> > includes:
> >
> > - A new left nav that contains the lists of items previously in the top
> > pulldown. It's easy to change what items are displayed, you can nest
> > arbitrary items, etc. The left nav is scrollable on small windows, so you
> > can always reach everything. Users can now jump between programming guide
> > sections easily.
> > - On the right is a list of the sections within a page, so you can
> quickly
> > jump to where you want. The list is autogenerated from the sections in
> the
> > page.
> > - Mobile improvements such as: you can now get to the top nav items from
> > the home page.
> >
> > This PR [2] would just be the first step. Once merged, it opens up other
> > improvements:
> >
> > - Break apart the major sections of the programming guide into separate
> > pages. This allows for the addition of more details and code samples for
> > each section, without making an already-too-large page even larger. With
> > the left nav, jumping between these pages will be easy.
> > - A proper overview landing page for the SDKs section, that lists the
> > available SDKs, any differences, etc.
> > - Tweaking left nav items to bubble up previously hard-to-find content
> (for
> > example, the Python type safety and Python dependencies pages)
> >
> > Please check it out and see what you think -- we'd love to get your
> > feedback.
> >
> > Thanks!
> >
> > [1] http://apache-beam-website-pull-requests.storage.
> > googleapis.com/332/index.html
> > [2] https://github.com/apache/beam-site/pull/332
> >
>
Re: [Proposal] Beam website navigation update
Posted by Reuven Lax <re...@google.com.INVALID>.
+1 Good documentation is just as important as good code. Thanks for all the
time you've put into this!
On Tue, Oct 17, 2017 at 2:07 PM, Kenneth Knowles <kl...@google.com.invalid>
wrote:
> This looks so good. Definitely makes the website more understandable, and
> especially invites more documentation to be written!
>
> I'll try to have some more concrete feedback on the PR.
>
> Kenn
>
> On Mon, Oct 16, 2017 at 2:23 PM, Melissa Pashniak <
> melissapa@google.com.invalid> wrote:
>
> > Hello Beam folks,
> >
> > I've received some good feedback that the Beam website can be difficult
> to
> > navigate, due to such things as:
> >
> > - The top pulldown menus are too long and you can't select things at the
> > end, and this will only get worse as we create more pages
> > - The programming guide as a single page is too long and difficult to
> > navigate
> > - Navigation issues on mobile devices
> >
> > In order to tackle these issues, we (myself and David Perez) have put
> > together a staged proposal [1] for an improved navigation story. It
> > includes:
> >
> > - A new left nav that contains the lists of items previously in the top
> > pulldown. It's easy to change what items are displayed, you can nest
> > arbitrary items, etc. The left nav is scrollable on small windows, so you
> > can always reach everything. Users can now jump between programming guide
> > sections easily.
> > - On the right is a list of the sections within a page, so you can
> quickly
> > jump to where you want. The list is autogenerated from the sections in
> the
> > page.
> > - Mobile improvements such as: you can now get to the top nav items from
> > the home page.
> >
> > This PR [2] would just be the first step. Once merged, it opens up other
> > improvements:
> >
> > - Break apart the major sections of the programming guide into separate
> > pages. This allows for the addition of more details and code samples for
> > each section, without making an already-too-large page even larger. With
> > the left nav, jumping between these pages will be easy.
> > - A proper overview landing page for the SDKs section, that lists the
> > available SDKs, any differences, etc.
> > - Tweaking left nav items to bubble up previously hard-to-find content
> (for
> > example, the Python type safety and Python dependencies pages)
> >
> > Please check it out and see what you think -- we'd love to get your
> > feedback.
> >
> > Thanks!
> >
> > [1] http://apache-beam-website-pull-requests.storage.
> > googleapis.com/332/index.html
> > [2] https://github.com/apache/beam-site/pull/332
> >
>
Re: [Proposal] Beam website navigation update
Posted by Kenneth Knowles <kl...@google.com.INVALID>.
This looks so good. Definitely makes the website more understandable, and
especially invites more documentation to be written!
I'll try to have some more concrete feedback on the PR.
Kenn
On Mon, Oct 16, 2017 at 2:23 PM, Melissa Pashniak <
melissapa@google.com.invalid> wrote:
> Hello Beam folks,
>
> I've received some good feedback that the Beam website can be difficult to
> navigate, due to such things as:
>
> - The top pulldown menus are too long and you can't select things at the
> end, and this will only get worse as we create more pages
> - The programming guide as a single page is too long and difficult to
> navigate
> - Navigation issues on mobile devices
>
> In order to tackle these issues, we (myself and David Perez) have put
> together a staged proposal [1] for an improved navigation story. It
> includes:
>
> - A new left nav that contains the lists of items previously in the top
> pulldown. It's easy to change what items are displayed, you can nest
> arbitrary items, etc. The left nav is scrollable on small windows, so you
> can always reach everything. Users can now jump between programming guide
> sections easily.
> - On the right is a list of the sections within a page, so you can quickly
> jump to where you want. The list is autogenerated from the sections in the
> page.
> - Mobile improvements such as: you can now get to the top nav items from
> the home page.
>
> This PR [2] would just be the first step. Once merged, it opens up other
> improvements:
>
> - Break apart the major sections of the programming guide into separate
> pages. This allows for the addition of more details and code samples for
> each section, without making an already-too-large page even larger. With
> the left nav, jumping between these pages will be easy.
> - A proper overview landing page for the SDKs section, that lists the
> available SDKs, any differences, etc.
> - Tweaking left nav items to bubble up previously hard-to-find content (for
> example, the Python type safety and Python dependencies pages)
>
> Please check it out and see what you think -- we'd love to get your
> feedback.
>
> Thanks!
>
> [1] http://apache-beam-website-pull-requests.storage.
> googleapis.com/332/index.html
> [2] https://github.com/apache/beam-site/pull/332
>
Re: [Proposal] Beam website navigation update
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Great news !
Thanks for the update.
Regards
JB
On Oct 27, 2017, 20:48, at 20:48, Melissa Pashniak <me...@google.com.INVALID> wrote:
>Thanks everyone! We'll move forward on this first round of changes, and
>then can iterate. Prabeesh, that's a great suggestion, I'll add that to
>the
>followup improvements list.
>
>
>On Tue, Oct 24, 2017 at 8:50 AM, Etienne Chauchot <ec...@gmail.com>
>wrote:
>
>> +1
>>
>> This is great!
>>
>> Thanks for all the work done.
>>
>>
>>
>> Le 20/10/2017 à 08:44, Prabeesh K. a écrit :
>>
>>> +1
>>>
>>> Great job, Melissa.
>>>
>>> It would be nice to have left or right navigation for *blog
>>> <https://apache-beam-website-pull-requests.storage.googleapi
>>> s.com/332/blog/index.html>*
>>> tab with recent posts or categories
>>>
>>> Regards,
>>> Prabeesh K.
>>>
>>>
>>> On 20 October 2017 at 09:30, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> wrote:
>>>
>>> +1
>>>>
>>>> It looks great.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 10/16/2017 11:23 PM, Melissa Pashniak wrote:
>>>>
>>>> Hello Beam folks,
>>>>>
>>>>> I've received some good feedback that the Beam website can be
>difficult
>>>>> to
>>>>> navigate, due to such things as:
>>>>>
>>>>> - The top pulldown menus are too long and you can't select things
>at the
>>>>> end, and this will only get worse as we create more pages
>>>>> - The programming guide as a single page is too long and difficult
>to
>>>>> navigate
>>>>> - Navigation issues on mobile devices
>>>>>
>>>>> In order to tackle these issues, we (myself and David Perez) have
>put
>>>>> together a staged proposal [1] for an improved navigation story.
>It
>>>>> includes:
>>>>>
>>>>> - A new left nav that contains the lists of items previously in
>the top
>>>>> pulldown. It's easy to change what items are displayed, you can
>nest
>>>>> arbitrary items, etc. The left nav is scrollable on small windows,
>so
>>>>> you
>>>>> can always reach everything. Users can now jump between
>programming
>>>>> guide
>>>>> sections easily.
>>>>> - On the right is a list of the sections within a page, so you can
>>>>> quickly
>>>>> jump to where you want. The list is autogenerated from the
>sections in
>>>>> the
>>>>> page.
>>>>> - Mobile improvements such as: you can now get to the top nav
>items from
>>>>> the home page.
>>>>>
>>>>> This PR [2] would just be the first step. Once merged, it opens up
>other
>>>>> improvements:
>>>>>
>>>>> - Break apart the major sections of the programming guide into
>separate
>>>>> pages. This allows for the addition of more details and code
>samples for
>>>>> each section, without making an already-too-large page even
>larger. With
>>>>> the left nav, jumping between these pages will be easy.
>>>>> - A proper overview landing page for the SDKs section, that lists
>the
>>>>> available SDKs, any differences, etc.
>>>>> - Tweaking left nav items to bubble up previously hard-to-find
>content
>>>>> (for
>>>>> example, the Python type safety and Python dependencies pages)
>>>>>
>>>>> Please check it out and see what you think -- we'd love to get
>your
>>>>> feedback.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> [1] http://apache-beam-website-pull-requests.storage.
>>>>> googleapis.com/332/index.html
>>>>> [2] https://github.com/apache/beam-site/pull/332
>>>>>
>>>>>
>>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>
Re: [Proposal] Beam website navigation update
Posted by Melissa Pashniak <me...@google.com.INVALID>.
Thanks everyone! We'll move forward on this first round of changes, and
then can iterate. Prabeesh, that's a great suggestion, I'll add that to the
followup improvements list.
On Tue, Oct 24, 2017 at 8:50 AM, Etienne Chauchot <ec...@gmail.com>
wrote:
> +1
>
> This is great!
>
> Thanks for all the work done.
>
>
>
> Le 20/10/2017 à 08:44, Prabeesh K. a écrit :
>
>> +1
>>
>> Great job, Melissa.
>>
>> It would be nice to have left or right navigation for *blog
>> <https://apache-beam-website-pull-requests.storage.googleapi
>> s.com/332/blog/index.html>*
>> tab with recent posts or categories
>>
>> Regards,
>> Prabeesh K.
>>
>>
>> On 20 October 2017 at 09:30, Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>
>> +1
>>>
>>> It looks great.
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 10/16/2017 11:23 PM, Melissa Pashniak wrote:
>>>
>>> Hello Beam folks,
>>>>
>>>> I've received some good feedback that the Beam website can be difficult
>>>> to
>>>> navigate, due to such things as:
>>>>
>>>> - The top pulldown menus are too long and you can't select things at the
>>>> end, and this will only get worse as we create more pages
>>>> - The programming guide as a single page is too long and difficult to
>>>> navigate
>>>> - Navigation issues on mobile devices
>>>>
>>>> In order to tackle these issues, we (myself and David Perez) have put
>>>> together a staged proposal [1] for an improved navigation story. It
>>>> includes:
>>>>
>>>> - A new left nav that contains the lists of items previously in the top
>>>> pulldown. It's easy to change what items are displayed, you can nest
>>>> arbitrary items, etc. The left nav is scrollable on small windows, so
>>>> you
>>>> can always reach everything. Users can now jump between programming
>>>> guide
>>>> sections easily.
>>>> - On the right is a list of the sections within a page, so you can
>>>> quickly
>>>> jump to where you want. The list is autogenerated from the sections in
>>>> the
>>>> page.
>>>> - Mobile improvements such as: you can now get to the top nav items from
>>>> the home page.
>>>>
>>>> This PR [2] would just be the first step. Once merged, it opens up other
>>>> improvements:
>>>>
>>>> - Break apart the major sections of the programming guide into separate
>>>> pages. This allows for the addition of more details and code samples for
>>>> each section, without making an already-too-large page even larger. With
>>>> the left nav, jumping between these pages will be easy.
>>>> - A proper overview landing page for the SDKs section, that lists the
>>>> available SDKs, any differences, etc.
>>>> - Tweaking left nav items to bubble up previously hard-to-find content
>>>> (for
>>>> example, the Python type safety and Python dependencies pages)
>>>>
>>>> Please check it out and see what you think -- we'd love to get your
>>>> feedback.
>>>>
>>>> Thanks!
>>>>
>>>> [1] http://apache-beam-website-pull-requests.storage.
>>>> googleapis.com/332/index.html
>>>> [2] https://github.com/apache/beam-site/pull/332
>>>>
>>>>
>>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>
Re: [Proposal] Beam website navigation update
Posted by Etienne Chauchot <ec...@gmail.com>.
+1
This is great!
Thanks for all the work done.
Le 20/10/2017 à 08:44, Prabeesh K. a écrit :
> +1
>
> Great job, Melissa.
>
> It would be nice to have left or right navigation for *blog
> <https://apache-beam-website-pull-requests.storage.googleapis.com/332/blog/index.html>*
> tab with recent posts or categories
>
> Regards,
> Prabeesh K.
>
>
> On 20 October 2017 at 09:30, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
>> +1
>>
>> It looks great.
>>
>> Regards
>> JB
>>
>>
>> On 10/16/2017 11:23 PM, Melissa Pashniak wrote:
>>
>>> Hello Beam folks,
>>>
>>> I've received some good feedback that the Beam website can be difficult to
>>> navigate, due to such things as:
>>>
>>> - The top pulldown menus are too long and you can't select things at the
>>> end, and this will only get worse as we create more pages
>>> - The programming guide as a single page is too long and difficult to
>>> navigate
>>> - Navigation issues on mobile devices
>>>
>>> In order to tackle these issues, we (myself and David Perez) have put
>>> together a staged proposal [1] for an improved navigation story. It
>>> includes:
>>>
>>> - A new left nav that contains the lists of items previously in the top
>>> pulldown. It's easy to change what items are displayed, you can nest
>>> arbitrary items, etc. The left nav is scrollable on small windows, so you
>>> can always reach everything. Users can now jump between programming guide
>>> sections easily.
>>> - On the right is a list of the sections within a page, so you can quickly
>>> jump to where you want. The list is autogenerated from the sections in the
>>> page.
>>> - Mobile improvements such as: you can now get to the top nav items from
>>> the home page.
>>>
>>> This PR [2] would just be the first step. Once merged, it opens up other
>>> improvements:
>>>
>>> - Break apart the major sections of the programming guide into separate
>>> pages. This allows for the addition of more details and code samples for
>>> each section, without making an already-too-large page even larger. With
>>> the left nav, jumping between these pages will be easy.
>>> - A proper overview landing page for the SDKs section, that lists the
>>> available SDKs, any differences, etc.
>>> - Tweaking left nav items to bubble up previously hard-to-find content
>>> (for
>>> example, the Python type safety and Python dependencies pages)
>>>
>>> Please check it out and see what you think -- we'd love to get your
>>> feedback.
>>>
>>> Thanks!
>>>
>>> [1] http://apache-beam-website-pull-requests.storage.
>>> googleapis.com/332/index.html
>>> [2] https://github.com/apache/beam-site/pull/332
>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
Re: [Proposal] Beam website navigation update
Posted by "Prabeesh K." <pr...@gmail.com>.
+1
Great job, Melissa.
It would be nice to have left or right navigation for *blog
<https://apache-beam-website-pull-requests.storage.googleapis.com/332/blog/index.html>*
tab with recent posts or categories
Regards,
Prabeesh K.
On 20 October 2017 at 09:30, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> +1
>
> It looks great.
>
> Regards
> JB
>
>
> On 10/16/2017 11:23 PM, Melissa Pashniak wrote:
>
>> Hello Beam folks,
>>
>> I've received some good feedback that the Beam website can be difficult to
>> navigate, due to such things as:
>>
>> - The top pulldown menus are too long and you can't select things at the
>> end, and this will only get worse as we create more pages
>> - The programming guide as a single page is too long and difficult to
>> navigate
>> - Navigation issues on mobile devices
>>
>> In order to tackle these issues, we (myself and David Perez) have put
>> together a staged proposal [1] for an improved navigation story. It
>> includes:
>>
>> - A new left nav that contains the lists of items previously in the top
>> pulldown. It's easy to change what items are displayed, you can nest
>> arbitrary items, etc. The left nav is scrollable on small windows, so you
>> can always reach everything. Users can now jump between programming guide
>> sections easily.
>> - On the right is a list of the sections within a page, so you can quickly
>> jump to where you want. The list is autogenerated from the sections in the
>> page.
>> - Mobile improvements such as: you can now get to the top nav items from
>> the home page.
>>
>> This PR [2] would just be the first step. Once merged, it opens up other
>> improvements:
>>
>> - Break apart the major sections of the programming guide into separate
>> pages. This allows for the addition of more details and code samples for
>> each section, without making an already-too-large page even larger. With
>> the left nav, jumping between these pages will be easy.
>> - A proper overview landing page for the SDKs section, that lists the
>> available SDKs, any differences, etc.
>> - Tweaking left nav items to bubble up previously hard-to-find content
>> (for
>> example, the Python type safety and Python dependencies pages)
>>
>> Please check it out and see what you think -- we'd love to get your
>> feedback.
>>
>> Thanks!
>>
>> [1] http://apache-beam-website-pull-requests.storage.
>> googleapis.com/332/index.html
>> [2] https://github.com/apache/beam-site/pull/332
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [Proposal] Beam website navigation update
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
It looks great.
Regards
JB
On 10/16/2017 11:23 PM, Melissa Pashniak wrote:
> Hello Beam folks,
>
> I've received some good feedback that the Beam website can be difficult to
> navigate, due to such things as:
>
> - The top pulldown menus are too long and you can't select things at the
> end, and this will only get worse as we create more pages
> - The programming guide as a single page is too long and difficult to
> navigate
> - Navigation issues on mobile devices
>
> In order to tackle these issues, we (myself and David Perez) have put
> together a staged proposal [1] for an improved navigation story. It
> includes:
>
> - A new left nav that contains the lists of items previously in the top
> pulldown. It's easy to change what items are displayed, you can nest
> arbitrary items, etc. The left nav is scrollable on small windows, so you
> can always reach everything. Users can now jump between programming guide
> sections easily.
> - On the right is a list of the sections within a page, so you can quickly
> jump to where you want. The list is autogenerated from the sections in the
> page.
> - Mobile improvements such as: you can now get to the top nav items from
> the home page.
>
> This PR [2] would just be the first step. Once merged, it opens up other
> improvements:
>
> - Break apart the major sections of the programming guide into separate
> pages. This allows for the addition of more details and code samples for
> each section, without making an already-too-large page even larger. With
> the left nav, jumping between these pages will be easy.
> - A proper overview landing page for the SDKs section, that lists the
> available SDKs, any differences, etc.
> - Tweaking left nav items to bubble up previously hard-to-find content (for
> example, the Python type safety and Python dependencies pages)
>
> Please check it out and see what you think -- we'd love to get your
> feedback.
>
> Thanks!
>
> [1] http://apache-beam-website-pull-requests.storage.
> googleapis.com/332/index.html
> [2] https://github.com/apache/beam-site/pull/332
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com