Re: [boost] Proposed documentation convention for pre-accepted libs

Subject: Re: [boost] Proposed documentation convention for pre-accepted libs
From: Francisco José Tapia (fjtapia_at_[hidden])
Date: 2011-05-02 17:21:42

It could be a good idea to have a separate page for the documentation of the
proposed projects, with the same format, and when a project is accepted ,
you only need to move the documentation.
If you access to the documentation across the page of don't accepted
projects, it is clear, and don't need to make two documentations.

2011/5/2 Daniel James <dnljms_at_[hidden]>

> On 2 May 2011 21:11, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> >
> > There was work put into the doc tool chain to prevent automatic use of
> the
> > standard Boost logo when using Boostbook. Which obviously was
> circumvented,
> > or otherwise not used, in this case. There are options in the Boostbook
> > generation for one to indicate one of the alternate logos. I don't
> remember
> > what the default was changed to after I first changed though.
>
> The default is to have no logo outside of boost, which I think is what
> you set. I changed the settings for css and links. I also the name of
> the parameter as it wasn't just changing the logo. The details are in
> the documentation list archives. The countertree documentation is
> using the logo markup from the website, not from boostbook. So it's
> added by some sort of post-processing.
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost
>