Ack, thanks Ahmet for the suggestion. I think it's important to bring attention to this discussion separately, so I am going to for the thread to start one specific about the navigation design.
On Mon, 14 Dec 2020 at 17:49, Ahmet Altay <[email protected]> wrote: > > > On Mon, Dec 14, 2020 at 4:32 PM Griselda Cuevas <[email protected]> wrote: > >> Hi Ahmet, adding response inline. >> >> A question about the content. Design adds items for use cases, do we have >>> existing content that fits into that template? >>> >> Yes, the content will be curated from the use cases we got presented at >> Beam Summits. We are tracking who has given permission to do this in Jira: >> BEAM-11225 <https://issues.apache.org/jira/browse/BEAM-11225> [1] >> > > Nice! > > >> >> Re: left navigation on the docs page. The fonts here are more readable to >>> me and the search feature is great. One question, the current version has >>> hierarchical and collapsible items on the left navigation. Would that still >>> be possible. IMO visual grouping, and hiding detailed items makes the >>> documentation easier to navigate. >>> >> >> This is the point we would like to hear feedback on, the proposal is to >> remove the full detail in the left navigation and leave the hierarchy view >> on the right navigation, which appears on the right when you click on a >> topic. Doing this will allow us to keep the left navigation organized and >> focused on the high level topics, hoping to make the experience smoother >> and neater for people and do not overwhelm them with so many >> topics/subtopics. >> > > Got it. Having a simplified left nav, and a more detailed right nav make > sense to me. > > My _very personal opinion_ is that the left nav is useful, and the right > nav is usually cluttered and has duplicate information. For example in this > page ( > https://beam.apache.org/documentation/transforms/python/overview/#element-wise), > left nav has richer and collapsible information. Right nav has partial > information. Somewhat of an opposite example in this page ( > https://beam.apache.org/documentation/programming-guide/#triggers). I > wonder if we can have a single nav menu in a more elegant way? > > >> >> For context, experienced UX and UI designers are proposing these changes >> and have optimized for a better discovery and troubleshooting experience, >> hence the recommendation. >> >> [1] >> https://issues.apache.org/jira/browse/BEAM-11225?jql=project%20%3D%20BEAM%20AND%20text%20~%20%22permission%20use%20cases%22 >> >>>
