mirror of
https://github.com/apache/zeppelin
synced 2026-05-24 09:38:26 +00:00
3 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
85d4df4f0c |
[ZEPPELIN-1219] Add searching feature to Zeppelin docs site
### What is this PR for? As more and more document pages are added, it's really hard to find specific pages. So I added searching feature to Zeppelin documentation site([jekyll](https://jekyllrb.com/) based site) using [lunr.js](http://lunrjs.com/). - **How does it work?** I created [`search_data.json`]( |
||
|
|
5975125f18 |
[ZEPPELIN-1018] Apply auto "Table of Contents" generator to Zeppelin docs website
### What is this PR for? I added auto TOC(Table of Contents) generator for Zeppelin documentation website. TOC can help people looking through whole contents at a glance and finding what they want quickly. I just added `<div id="toc"></div>` to the each documentation header. [`toc`](https://github.com/apache/zeppelin/compare/master...AhyoungRyu:ZEPPELIN-1018?expand=1#diff-85af09fb498a5667ea455391533f945dR3) recognize `<h2>` & `<h3>` as a title in the docs and it automatically generate TOC. So I set a rule for this work. (I'll write this rule on `docs/CONTRIBUTING.md` or [docs/howtocontributewebsite](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/howtocontributewebsite.html)). ``` # Level-1 Heading <- Use only for the main title of the page ## Level-2 Heading <- Start with this one ### Level-3 heading <- Only use this one for child of Level-2 toc only recognize Level-2 & Level-3 ``` Please see the below attached screenshot image. ### What type of PR is it? Improvement & Documentation ### Todos * [x] - Add TOC generator * [x] - Apply TOC(`<div id="toc"></div>`) to every documentation and reorganize each headers(apply the above rule) * [x] - Fix some broken code block in several docs * [x] - Apply TOC to `r.md` (Currently R docs has some duplicated info since [this one]( |
||
|
|
daab1f7f7a |
[ZEPPELIN-742] Add documentation for front-end AngularJS AP
### What is this PR for? This JIRA: * add documentation for the new paragraphId display in the paragraph command dialog. Instead of just adding some description to the paragraphId, I took the opportunity to also document the entire Zeppelin UI Layout and added a menu entry **UI Layout** under menu **QuickStart**. It is inspired by the content of the talk on Zeppelin at different conferences * rename the menu **Display System** / **Angular** to **Display System** / **Back-end Angular Interactions** * add a new entry **Front-end Angular Interactions** under the menu **Display System** to describe the new front-end AngularJS API introduced by this epic _This is a sub-task of epic **[ZEPPELIN-635]**_ ### What type of PR is it? [Documentation] ### Todos * [ ] - Check documentation ### What is the Jira issue? **[ZEPPELIN-6742]** ### How should this be tested? Build Zeppelin documentation locally and check ### Screenshots (if appropriate) New **QuickStart** / **UI Layout** documentation which mentions the **paragraphId**  New **Display System** / **Front-end Angular Interactions** menu to describe the new front-end AngularJS API introduced by this epic  ### Questions: * Does the licenses files need update? --> No * Is there breaking changes for older versions? --> No * Does this needs documentation? --> No [ZEPPELIN-635]: https://issues.apache.org/jira/browse/ZEPPELIN-635 [ZEPPELIN-742]: https://issues.apache.org/jira/browse/ZEPPELIN-742 Author: DuyHai DOAN <doanduyhai@gmail.com> Closes #865 from doanduyhai/ZEPPELIN-742 and squashes the following commits: |
Renamed from docs/displaysystem/angular.md (Browse further)