GitHub user beneficial02 reopened a pull request:

    https://github.com/apache/zeppelin/pull/2530

    [ZEPPELIN-2853] Change the order of contents in index document.

    ### What is this PR for?
    To change the order of content in index documentation. Now the last two 
contents is "External Resources" and "Available Interpreters". This PR change 
the order to "Available Interpreters" and "External Resources".
    
    ### What type of PR is it?
    [Documentation]
    
    ### What is the Jira issue?
    https://issues.apache.org/jira/browse/ZEPPELIN-2853
    
    ### How should this be tested?
    1. Read the doc
    
    ### Screenshots (if appropriate)
    Before
    
    <img width="726" alt="screen shot 2017-08-15 at 3 08 14 pm" 
src="https://user-images.githubusercontent.com/19610222/29304040-d9f9adac-81cb-11e7-9aa3-0a325511e267.png";>
    
    After
    
    <img width="615" alt="screen shot 2017-08-15 at 3 04 44 pm" 
src="https://user-images.githubusercontent.com/19610222/29304001-a26fca6a-81cb-11e7-8cf2-be10eef781d9.png";>
    
    ### Questions:
    * Does the licenses files need update? No
    * Is there breaking changes for older versions? No
    * Does this needs documentation? No


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

    $ git pull https://github.com/beneficial02/zeppelin feature/change_doc_order

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

    https://github.com/apache/zeppelin/pull/2530.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 #2530
    
----
commit 10a7172d905a960f10de3501c4abf4fd4978ac83
Author: Loun Lee <beneficia...@gmail.com>
Date:   2017-08-15T05:52:30Z

    feature: change the order of doc content
    
    There was a Travis error so amend last commit.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to