zeppelin/docs/quickstart/explorezeppelinui.md
Mina Lee 70ab1a376d [ZEPPELIN-952] Refine website style
### What is this PR for?
- update document style (font, line-spacing)
- apply same formats for documents
- fix broke document styles

### What type of PR is it?
Documentation

### What is the Jira issue?
[ZEPPELIN-952](https://issues.apache.org/jira/browse/ZEPPELIN-952)

### Screenshots (if appropriate)
**Before**
<img width="1184" alt="screen shot 2016-06-04 at 9 51 38 pm" src="https://cloud.githubusercontent.com/assets/8503346/15803667/d0dd5ac2-2a9f-11e6-9ed0-ddc369a97612.png">

**After**
<img width="1184" alt="screen shot 2016-06-04 at 9 15 08 pm" src="https://cloud.githubusercontent.com/assets/8503346/15803666/cd9212ea-2a9f-11e6-986e-17992a495ab6.png">

**Before**
<img width="1183" alt="screen shot 2016-06-04 at 10 08 53 pm" src="https://cloud.githubusercontent.com/assets/8503346/15803695/03e73126-2aa1-11e6-8675-3ca437aeb833.png">

**After**
<img width="1184" alt="screen shot 2016-06-04 at 10 08 18 pm" src="https://cloud.githubusercontent.com/assets/8503346/15803696/078ce866-2aa1-11e6-9044-4f5e16649eb4.png">

**Before**
<img width="1184" alt="screen shot 2016-06-04 at 10 10 47 pm" src="https://cloud.githubusercontent.com/assets/8503346/15803704/5787e9ba-2aa1-11e6-804c-076a8f3aa852.png">

**After**
<img width="1184" alt="screen shot 2016-06-04 at 10 11 22 pm" src="https://cloud.githubusercontent.com/assets/8503346/15803707/5afb5d0c-2aa1-11e6-98c7-7440db35bd2f.png">

**Before**
<img width="188" alt="screen shot 2016-06-04 at 10 12 36 pm" src="https://cloud.githubusercontent.com/assets/8503346/15803719/92e5cc3e-2aa1-11e6-9a9f-e12150e78733.png">

**After**
<img width="199" alt="screen shot 2016-06-04 at 10 12 55 pm" src="https://cloud.githubusercontent.com/assets/8503346/15803721/958e8c00-2aa1-11e6-8768-8350db6e7173.png">

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No

Author: Mina Lee <minalee@nflabs.com>

Closes #962 from minahlee/ZEPPELIN-952 and squashes the following commits:

f9bee91 [Mina Lee] Capitalize hawq
72481bd [Mina Lee] Update doc titles
495a074 [Mina Lee] remove old style.css
27ca869 [Mina Lee] use code block for file location in spark.md
eb821f1 [Mina Lee] Change file location and rename file
72f8ec3 [Mina Lee] change storage doc layout and fix pre block
4202208 [Mina Lee] Apply same format for rest api docs
5875066 [Mina Lee] split display page into text and html
8bc5a6e [Mina Lee] prettify document
0cb953e [Mina Lee] remove incubating tag
2016-06-08 11:44:26 -07:00

5 KiB

layout title description group
page Explore Zeppelin UI Description of Zeppelin UI Layout quickstart

Home Page

The first time you connect to Zeppelin, you'll land at the main page similar to the below screen capture

On the left of the page are listed all existing notes. Those notes are stored by default in the $ZEPPELIN_HOME/notebook folder.

You can filter them by name using the input text form. You can also create an new note, refresh the list of existing notes (in case you manually copy them into the $ZEPPELIN_HOME/notebook folder) and import a note.

When clicking on Import Note link, a new dialog open. From there you can import your note from local disk or from a remote location if you provide the URL.

By default, the name of the imported note is the same as the original note but you can override it by providing a new name.


## Menus

1. Notebook

The Notebook menu proposes almost the same features as the note management section in the home page. From the drop-down menu you can:

  1. Open a selected note
  2. Filter node by name
  3. Create a new note

2. Interpreter

In this menu you can:

  1. Configure existing interpreter instance
  2. Add/remove interpreter instances

3. Configuration

This menu displays all the Zeppelin configuration that are set in the config file $ZEPPELIN_HOME/conf/zeppelin-site.xml


## Note Layout

Each Zeppelin note is composed of 1 .. N paragraphs. The note can be viewed as a paragraph container.

Paragraph

Each paragraph consists of 2 sections: code section where you put your source code and result section where you can see the result of the code execution.

On the top-right corner of each paragraph there are some commands to:

  • execute the paragraph code
  • hide/show code section
  • hide/show result section
  • configure the paragraph

To configure the paragraph, just click on the gear icon:

From this dialog, you can (in descending order):

  • find the paragraph id ( 20150924-163507_134879501 )
  • control paragraph width. Since Zeppelin is using the grid system of Twitter Bootstrap, each paragraph width can be changed from 1 to 12
  • move the paragraph 1 level up
  • move the paragraph 1 level down
  • create a new paragraph
  • change paragraph title
  • show/hide line number in the code section
  • disable the run button for this paragraph
  • export the current paragraph as an iframe and open the iframe in a new window
  • clear the result section
  • delete the current paragraph

Note toolbar

At the top of the note, you can find a toolbar which exposes command buttons as well as configuration, security and display options.

On the far right is displayed the note name, just click on it to reveal the input form and update it.

In the middle of the toolbar you can find the command buttons:

  • execute all the paragraphs sequentially, in their display order
  • hide/show code section of all paragraphs
  • hide/show result section of all paragraphs
  • clear the result section of all paragraphs
  • clone the current note
  • export the current note to a JSON file. _Please note that the code section and result section of all paragraphs will be exported. If you have heavy data in the result section of some paragraphs, it is recommended to clean them before exporting
  • commit the current node content
  • delete the note
  • schedule the execution of all paragraph using a CRON syntax

On the right of the note tool bar you can find configuration icons:

  • display all the keyboard shorcuts
  • configure the interpreters binding to the current note
  • configure the note permissions
  • switch the node display mode between default, simple and report