GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1980
[gh-pages][ZEPPELIN-2061] Add Medium blog section to the main page
### What is this PR for?
There is "[Apache Zeppelin
Stories](https://medium.com/apache-zeppelin-stories)" channel in
[Medium](https://medium.com/). So I wanted to show the blog posts in this
Medium channel via Zeppelin website. To do this, I used AWS Lambda function:
[fetch-zeppelin-medium-story](https://github.com/AhyoungRyu/fetch-zeppelin-medium-story)
(read RSS feed -> converted it to JSON) and make it run per every 1 day. So
the result file
[medium.js](https://s3.amazonaws.com/apache-zeppelin/post/medium.js)(used js
file format to easily load to Zeppelin website) will be refreshed everyday.
Using this file I added "APACHE ZEPPELIN STORIES" section below the main page
of Zeppelin website.
The reason I did this way to read posts' info is
1. As
[Medium/medium-api-docs/issues/49](https://github.com/Medium/medium-api-docs/issues/49#issuecomment-229206837)
said, currently there is no API provided by Medium to get the list of blog
post info in Story channel ("Apache Zeppelin Stories" is _**Story**_ channel).
Instead Medium suggests to [use **RSS
feed**](https://help.medium.com/hc/en-us/articles/214874118-RSS-Feeds-of-publications-and-profiles).
2. I thought this way is more simple than adding jquery code to read RSS
feed -> convert to JSON -> reading each field and etc... like
[this](http://stackoverflow.com/questions/10943544/how-to-parse-an-rss-feed-using-javascript?answertab=votes#tab-top).
I thought this is overdoing to just add blog section to the website.
### What type of PR is it?
gh-pages
### What is the Jira issue?
[ZEPPELIN-2061](https://issues.apache.org/jira/browse/ZEPPELIN-2061)
### How should this be tested?
Build `gh-pages` branch as described in
[here](https://github.com/apache/zeppelin/tree/gh-pages#build-website). Or see
the below gif screenshot img :)
### 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 add/mediumBlogPostSection
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1980.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 #1980
----
commit 1cbbc28ce427e36055c036109896f80b22948a3f
Author: AhyoungRyu <[email protected]>
Date: 2017-02-06T15:29:45Z
Add moment.min.js for date formatting
commit 82cc48e0781f4a717b56e39451a6df297174c5be
Author: AhyoungRyu <[email protected]>
Date: 2017-02-06T15:30:11Z
Add Medium blog post section to Zeppelin website
commit fa5f6b0b280678919ac47bd7dee949769529cb2f
Author: AhyoungRyu <[email protected]>
Date: 2017-02-06T15:33:44Z
Remove unused CSS classes
----
---
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.
---
