Hi, If i add little bit more, You'll able to find Zeppelin homepage in branch 'gh-pages'. 'bundle exec jekyll build' command will generates deployable homepage under _site/ directory.
Thanks, moon On Sun, Jun 28, 2015 at 4:25 AM Eric Charles <[email protected]> wrote: > The link points to the zeppelin web site sources (ever tried to build > it, so I can not help you on this). > > I was just saying that markdown documentation could be embedded in > Zeppelin. You don't need to build the website to achieve this, but use a > specific interpreter that loads markdown resources/url. Hope this makes > it more clear. > > On 2015-06-28 12:46, IT CTO wrote: > > I looked at the code pointed above but could not run it. - from which > > directory do you do that? running bundle install on root directory fails > > "Could not locate Gemfile or .bundle/ directory" > > > > On Sun, Jun 28, 2015 at 1:16 PM Eric Charles <[email protected]> wrote: > > > >> I have developed an update to the markdown interpreter which reads a > >> file from the classpath or from an URL and displays it as HTML in the > >> notebook. > >> > >> The idea is to reuse as much as possible contents written in files and > >> make them available via specific notes (the "Use Guide" notes). > >> > >> This would work if we reuse the resources from > >> https://github.com/apache/incubator-zeppelin/tree/gh-pages (via a > >> packaged jar, or simply via URL). > >> > >> The limitation for now is the images which must be hosted on an > >> accessible URL. > >> > >> On 2015-06-28 09:12, IT CTO wrote: > >>> Hi, > >>> As we deploy zeppelin in our internal network we would like to have > some > >>> end-user documentation available within the network. > >>> I was thinking of trying to zip the documentation files in the > packaging > >>> and link it the the zeppelin web pages. > >>> > >>> 1) Do we want to do it for everyone or should I do it internally only? > >>> 2) Are we going to keep the documentation pages as is or move it to > >> another > >>> platform? > >>> 3) How can I get access to the documentation source files? > >>> > >>> Thanks, > >>> Eran > >>> > >> > > >
