I'm a fan of PDFs, too, for their searchability among other things.
There's no process in place, yet, for generating a good-looking PDF from
the Markdown sources. Something to put on the to-do list.
Right now, HTML format is the best presentation.

On Monday, October 17, 2016, William Markito <wmark...@pivotal.io> wrote:

> IHMO, it would be really nice to ship a PDF version of the docs.
>
> About the examples, if we could package and ship sources only for that
> module, that would be cool as well.
>
>
>
> On Mon, Oct 17, 2016 at 5:21 PM, Dan Smith <dsm...@pivotal.io
> <javascript:;>> wrote:
>
> > Along these lines, should we distributing the docs with the binary
> release?
> > Or maybe just providing a link to them? The README.md shipped with
> 1.0.RC2
> > points to http://geode.docs.pivotal.io/ .
> >
> > What about geode-examples? Should that be part of the binary release?
> >
> > -Dan
> >
> > On Mon, Oct 17, 2016 at 2:21 PM, Joey McAllister <jmcallis...@pivotal.io
> <javascript:;>>
> > wrote:
> >
> > > @Roman: Nothing that I can think of, apart from giving the community
> time
> > > to offer feedback here (which, it looks like, is all positive). William
> > > Markito and I were able to build and test a local version of the
> website
> > > with the docs included.
> > >
> > > Based on the +1s here, I'd like to go ahead and push the current docs
> to
> > > the website. I'll also document the process in a README.
> > >
> > > On Mon, Oct 17, 2016 at 12:49 PM Roman Shaposhnik <
> ro...@shaposhnik.org <javascript:;>>
> > > wrote:
> > >
> > > > On Mon, Oct 17, 2016 at 10:57 AM, Anthony Baker <aba...@pivotal.io
> <javascript:;>>
> > > wrote:
> > > > > Since the geode docs have now been merged to the develop branch,
> > let’s
> > > > start
> > > > > hosting them on http://geode.apache.org.  Thoughts?
> > > >
> > > > Huge +1! Anything stopping you from pushing the first update and
> start
> > > > maintaining
> > > > it a'la Hadoop:
> > > >     https://hadoop.apache.org/docs/
> > > > ?
> > > >
> > > > Thanks,
> > > > Roman.
> > > >
> > >
> >
>
>
>
> --
>
> ~/William
>

Reply via email to