Not sure if this is something to address in this thread or if I should file
a separate JIRA, but for some reason, accessing the site over https gets
rid of the pretty CSS. Seems to happen in Chrome and Firefox. Anyone have a
clue why?

-Dima

On Wed, Dec 17, 2014 at 10:53 AM, Nick Dimiduk <ndimi...@gmail.com> wrote:

> Tweaking the layout of the website goes one of two ways. Either there's a
> configuration point exposed from the maven skin or there isn't. If there
> is, it's simply editing the appropriate custom tag in site.xml. If not,
> we'll need to bring back the velocity site.vm template. Configurations are
> documented here:
> http://andriusvelykis.github.io/reflow-maven-skin/skin/config.html
>
> Tweaking visuals is now based on the theme. We can either choose another
> bootswatch theme, or write our own. That stuff is documented here:
> http://andriusvelykis.github.io/reflow-maven-skin/skin/themes/
>
> Right now the site is separate from the book. In theory we could move book
> content over to become site content, in which case it would be managed by
> this same plugin. Short of that, we get into applying style via the docbook
> plugin. I've looked into this a bit; it's not nearly as easy as applying
> reflow-maven-skin. The current leads I have for this are
> https://github.com/lcahlander/docbook and
>
> https://github.com/pmartin/phing-documentation-docbook/commit/8d8f0b81951c4e07420083b204599a6b9ef00537
>  .
>
> Honestly though, if we're looking at moving away from docbook, I think we
> should consider a more modern toolset, Sphinx-doc, for example:
> http://sphinx-doc.org
>
> On Tue, Dec 16, 2014 at 8:21 PM, Misty Stanley-Jones <
> mstanleyjo...@cloudera.com> wrote:
> >
> > Absolutely fantastic!!! Got pointers to how tweaking the website would
> > work?
> >
> > In the new year I hope to really get started on a restructure of the Ref
> > Guide. I've thought about asking to move to AsciiDOC or MarkDown but I'd
> > like to do a proof-of-concept and see if it really gets us anything we
> > don't already have with Docbook. It's less of a potential value since we
> > are not hosted on Github, which has great integration with AsciiDOC and
> > MarkDown. I'm very interested in improving the look and feel of the doc.
> I
> > think a lot of it will be structural -- reorganizing and re-chunking
> > content.
> >
> > In the meantime, theming the Docbook is not as hard as you might think.
> > Have a look at the XSLT files. (I know, famous last words).
> >
> > On Wed, Dec 17, 2014 at 1:21 PM, Nick Dimiduk <ndimi...@gmail.com>
> wrote:
> >
> > > For those not following closely in JIRAland, I've two changes that are
> > > ready to go. First, there's transition over to a bootstrap-based layout
> > for
> > > our home page. This work is done in HBASE-12688. This improves the
> looks
> > of
> > > things and will make it pretty easy to update our look-and-feel in the
> > > future. Second, I fixed a build problem where the online book wasn't
> > > getting its intended styling. This is done in HBASE-12687. I'd like to
> > > update the book to look the same as the front-page, but getting styles
> > into
> > > docbook is proving non-trivial.
> > >
> > > Anyway, both of these changes are pushed to master and we're ready for
> a
> > > site re-build with the new look. I'll make that happen tomorrow morning
> > > unless I hear actionable objections.
> > >
> > > You can get a preview of things to come over one
> > > http://people.apache.org/~ndimiduk/site/
> > >
> > > Thanks,
> > > Nick
> > >
> > > On Fri, Dec 5, 2014 at 12:29 PM, Stack <st...@duboce.net> wrote:
> > > >
> > > > Thanks. I've been having a dialog w/ your crew that has been going
> on a
> > > > while... was wondering if any progress.
> > > > Grand,
> > > > St.Ack
> > > >
> > > > On Fri, Dec 5, 2014 at 11:55 AM, Ryan Rawson <ryano...@gmail.com>
> > wrote:
> > > >
> > > > > I'm checking to see if our marketing and web team can help.  The
> > > > > primary requirement is going to be ditching the mvn:site from the
> > > > > front page.  "reskinning it" might not be so easy.
> > > > >
> > > > > -ryan
> > > > >
> > > > > On Thu, Dec 4, 2014 at 9:52 AM, lars hofhansl <la...@apache.org>
> > > wrote:
> > > > > > +1
> > > > > > I just came across one of the various HBase vs. Cassandra
> articles,
> > > and
> > > > > one of the main tenants of the articles was how much better the
> > > Cassandra
> > > > > documentation was.Thank god we have Misty now. :)
> > > > > >
> > > > > > (not sure how much just a skin would help, but it surely won't
> > hurt)
> > > > > >
> > > > > > -- Lars
> > > > > >       From: Nick Dimiduk <ndimi...@gmail.com>
> > > > > >  To: hbase-dev <dev@hbase.apache.org>
> > > > > >  Sent: Tuesday, December 2, 2014 9:46 AM
> > > > > >  Subject: A face-lift for 1.0
> > > > > >
> > > > > > Heya,
> > > > > >
> > > > > > In mind of the new release, I was thinking we should clean up our
> > > act a
> > > > > > little bit in regard to hbase.apache.org and our book. Just
> > because
> > > > the
> > > > > > project started in 2007 doesn't mean we need a site that looks
> like
> > > > it's
> > > > > > from 2007. Phoenix's site looks great in this regard.
> > > > > >
> > > > > > For the home page, I was thinking of converting it over to
> > bootstrap
> > > > [0]
> > > > > so
> > > > > > that it'll be easier to pick up theme, either on of our own or
> > > > something
> > > > > > pre-canned [1]. I'm no web designer, but the idea is this would
> > make
> > > it
> > > > > > easier for someone who is to help us out.
> > > > > >
> > > > > > For the book, I just want to skin it -- no intention of changing
> > > > docbook
> > > > > > part (such a decision I'll leave up to Misty). I'm less sure on
> > this
> > > > > > project, but Riak's docs are a nice inspiration.
> > > > > >
> > > > > > What do you think? Do we know any web designers who can help out
> > with
> > > > the
> > > > > > CSS?
> > > > > >
> > > > > > -n
> > > > > >
> > > > > > [0]: http://getbootstrap.com
> > > > > > [1]: https://wrapbootstrap.com/
> > > > > > [2]: http://docs.basho.com/riak/latest/
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to