GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1855
[ZEPPELIN-1913] Separate "Apache Zeppelin Configuration" from quickstart
page
### What is this PR for?
I think [Quick
Start](https://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/install/install.html)
page should contain minimum contents to get start Zeppelin for beginners. If
not, this can be making the entrance barrier high. But after "SSL
configuration" contents were added, configuration section came so long. So I
created new page `configuration.md` and separated the all configuration related
contents from Quick Start page.
### What type of PR is it?
Documentation
### What is the Jira issue?
[ZEPPELIN-1913](https://issues.apache.org/jira/browse/ZEPPELIN-1913)
### How should this be tested?
Outline the steps to test the PR here.
### Screenshots (if appropriate)
- before (quickstart guide + Zeppelin configuration in one page)
- after (separated two page)
### 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/AhyoungRyu/zeppelin separate/confContents
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1855.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 #1855
----
commit 9d0cb197e7971ebf644dee3506b551a8976ad089
Author: AhyoungRyu <[email protected]>
Date: 2017-01-06T05:31:44Z
Separate 'Zeppelin Configuration' section from quickstart
commit 54f9ad9fb50fe00f18ca0c8163e0abfe51097cc7
Author: AhyoungRyu <[email protected]>
Date: 2017-01-06T05:35:40Z
Update page description
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
