GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1935
[gh-pages][ZEPPELIN-1973] List all available Helium packages under
zeppelin.apache.org
### What is this PR for?
After #1842 merged, anyone can create his/her own `VISUALIZATION` pkg as
described in [Writing a new
Visualization](https://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/development/writingzeppelinvisualization.html)
and can publish it to npm registry. The below img describes "the current
Helium package mechanism(black outline) + proposing from me to list all Helium
pkgs published in npm registry(red one) in Zeppelin official website". So what
I did to do this was the red-outlined factors.
<img width="1273" alt="screen shot 2017-01-24 at 2 15 45 am"
src="https://cloud.githubusercontent.com/assets/10060731/22231364/7d935b48-e226-11e6-98ff-3b642fbffc35.png";>
**Future work**
Currently to enable/disable the helium VIZ pkg via Helium GUI menu in
Zeppelin, user needs to place Helium info json files under
`ZEPPELIN_HOME/helium/` manually. But from now, we can substitute this not user
friendly way by using `helium.js`. (Will handle in another PR )
**Any issues?**
But as I mentioned in
[ZEPPELIN-1973](https://issues.apache.org/jira/browse/ZEPPELIN-1973), since I
used AWS services (Lambda, S3 and CloudWatch), I needed an account. So for
continous management, I'm willing to share the information that need to
run/packaging/deploy Lambda function with Zeppelin PMCs if you Zeppelin
community thinks I need to do it.
### What type of PR is it?
Improvement | Feature
### Todos
* [ ] - Adjust navbar when screen width is small
### What is the Jira issue?
[ZEPPELIN-1973](https://issues.apache.org/jira/browse/ZEPPELIN-1973)
### How should this be tested?
Build `gh-pages` branch as described in
[here](https://github.com/apache/zeppelin/tree/gh-pages#build-website). Or
please see the below gif sreenshot :)
### Screenshots (if appropriate)
### 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 gh-page/ZEPPELIN-1973
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1935.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 #1935
----
commit b1d7ffd6826e862a89b519365af42c8230beabcb
Author: AhyoungRyu <[email protected]>
Date: 2017-01-23T15:54:53Z
Import js files: icons, angular, helium package list info
commit a5f09260bf11f1a5fcbde140412e43018b5a84de
Author: AhyoungRyu <[email protected]>
Date: 2017-01-23T15:56:51Z
Add 'Helium' menu to main navbar
commit 45c0e7d2fe9bd8c76aee92aa194c9e04110a8f84
Author: AhyoungRyu <[email protected]>
Date: 2017-01-23T15:57:08Z
Add new page: Helium Packages
commit 129a916fd97e4483dd6f1b056f5420f7d79d7c70
Author: AhyoungRyu <[email protected]>
Date: 2017-01-23T15:57:41Z
Styling
----
---
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.
---
![https://cloud.githubusercontent.com/assets/10060731/22231364/7d935b48-e226-11e6-98ff-3b642fbffc35.png"](https://cloud.githubusercontent.com/assets/10060731/22231364/7d935b48-e226-11e6-98ff-3b642fbffc35.png"){kind=link}
