[ 
https://issues.apache.org/jira/browse/QUARKS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243939#comment-15243939
 ] 

ASF GitHub Bot commented on QUARKS-145:
---------------------------------------

GitHub user queeniema opened a pull request:

    https://github.com/apache/incubator-quarks-website/pull/43

    [QUARKS-145] Highlight current page in sidebar and keep sidebar open

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/queeniema/incubator-quarks-website QUARKS-145

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-quarks-website/pull/43.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #43
    
----
commit a6166a11595098e0351147e91ff921da182653dd
Author: Queenie Ma <[email protected]>
Date:   2016-04-16T01:43:47Z

    [QUARKS-145] Highlight current page in sidebar and keep sidebar open

----


> Highlight current page in sidebar and keep sidebar open
> -------------------------------------------------------
>
>                 Key: QUARKS-145
>                 URL: https://issues.apache.org/jira/browse/QUARKS-145
>             Project: Quarks
>          Issue Type: Improvement
>          Components: Documentation, Web Site
>            Reporter: Queenie Ma
>            Assignee: Queenie Ma
>
> Currently, when clicking an item (e.g., "How to participate"), the sidebar 
> closes immediately and none of the items are visible. Highlighting the 
> current item in the sidebar and keeping the sidebar open after clicking on an 
> item would:
> # allow users to locate where they are relative to other pages
> # allow users to easily see what other content is available in the current 
> section (this would be especially useful when looking at a recipe)
> # provide a more intuitive user experience



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to