[publican-list] Branding not applied when using --embedtoc with Publican 3.1.5

[Jeff Fearn]

On 05/17/2013 11:08 AM, James Pooton wrote:
> On Thu, May 16, 2013 at 4:55 PM, Jeff Fearn <jfearn at redhat.com> wrote:
>>
>>
>> --embedtoc basically means "build this to use in a publican web site". The
>> website contains the missing content. It's done this way so that you can
>> change the style on a web site without having to rebuild every book or
>> replace a mass of files.
>>
>> http://jfearn.fedorapeople.**org/en-US/Publican/3.0/html/**
>> Users_Guide/sect-Users_Guide-**Website.html
>>
>> <http://jfearn.fedorapeople.org/en-US/Publican/3.0/html/Users_Guide/sect-Users_Guide-Website.html>
>
>
> That's actually the page I was working through. :)  I guess my question is
> this.  That doc states:
>
> "The Publican-generated home page is the localizable page to which visitors
> are directed by the site JavaScript and which **provides the style** for
> the website structure."
>
> So I created a home page article per the directions, adding "web_type:
> home" and "brand: videoNEXT" to its publican.cfg.  However, when building
> it for install, instructions ask for the following:
>
> publican build --publish --formats html-single --embedtoc --langs all
>
> Which results in HTML without any brand/style content applied, apparently
> because of the --embedtoc.(?)  So installing this into the website doesn't
> seem to bring with our brand/style information.  I'm sure I'm missing
> something simple here, but what part of the process supplies the
> brand/style css and (common_content) images to the web doc root?  I was
> assuming it came with the home page article, or is it supposed to be
> manually gathered?
>
> To be clear, after going through the process of create_site, adding a home
> page article, and one other book. (both added to the web site). I can see
> the "content" from the home page and book doc when browsing, but there are
> lots of 404s as you'll see below:
>
> /common/en-US/css/menu.css
> /videoNEXT/en-US/css/menu.css
> /en-US/labels.js
> /footer.html
> /videoNEXT/en-US/images/image_left.png
> /videoNEXT/en-US/images/image_right.png
> /en-US/images/web_logo.png
> /common.css
> /overrides.css
> /lang.css

Gah! Looks like some steps are missing for changes introduced in 3.1.

RPM sites:

$ yum install publican-web publican-$brand-web
$ publican update_site


For manual sites:

$ cd $brandsrc_dir (yes including the common brand in the publican source >_<)
$ publican build --formats=xml --langs=all --publish    # brands don't use embedtoc
$ publican install_brand --web --path=$path_to_site_root_dir
# repeat for all brands
$ publican update_site --site_config $path_to_site_cfg

You might want to try setting web_style in your site cfg to 2 and run update_site for a different look. This is also not in the PUG but is documented in 'publican help_config'.

$ publican help_config | grep -A3 web_style
	web_style:
		Splash pages should be generated to be compatible with this web style. Valid values are 1 and 2.
		Default: 1
		Constraint: [1-2]

Which is actually a pretty sad description given '2' is an entirely different web layout :-(

Cheers, Jeff
.
-- 
Jeff Fearn <jfearn at redhat.com>
Senior Software Engineer
Infrastructure Engineering & Development (AEU)
Red Hat Asia Pacific Pty Ltd
GPG: 0x0357E8F0