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

ASF GitHub Bot commented on FLINK-3132:
---------------------------------------

Github user uce commented on the pull request:

    https://github.com/apache/flink/pull/1499#issuecomment-171727541
  
    I didn't notice before, but now I also see that it can feel strange when 
you scroll down. The text looks right aligned relative to the top navigation 
bar. But moving the sub navigation to the top might result in confusion when 
having two lists (sub navigation and per page table of contents). Personally, I 
would keep it on the left for now. If others feel that it should be moved to 
the top, I'm happy to do it though. :) The static navigation was a problem for 
the reason Till mentioned. Do you have another idea?
    
    Regarding the code examples: they will be smaller again with Fabians 
suggested change. I can then do another pass over the code examples. In 
general, the more narrow text was something that some users were asking for in 
the past.


> Restructure streaming guide
> ---------------------------
>
>                 Key: FLINK-3132
>                 URL: https://issues.apache.org/jira/browse/FLINK-3132
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 0.10.1
>            Reporter: Ufuk Celebi
>            Assignee: Ufuk Celebi
>             Fix For: 1.0.0
>
>
> The streaming guide is in parts very cluttered and overloaded.
> I think it needs a restructuring and de-cluttering by splitting it up into 
> multiple pages.
> This will make it easier to navigate to the relevant parts of it. It will 
> also improve the custom search. At the moment you often end up on the single 
> long page streaming guide, where you still need to find it manually.
> Some introductory notes about the main concepts are missing as well.



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

Reply via email to