<div dir="ltr">Thanks! Getting closer, but still missing some resources after these new steps. I decided to start fresh:<div><br></div><div style>- Updated to publican-3.1.5-3.fc18.noarch</div><div style>- Updated to patched FC18 builds of wkhtmltopdf packages</div>
<div style>- Created a new "web site" via:</div><div style><br></div><div style><div>$ mkdir /videonext/webdocs</div><div>$ cd /videonext/webdocs</div><div>$ publican create_site --site_config webdocs.cfg --db_file webdocs.db --toc_path html/docs</div>
<div><br></div><div style>- Added the following to webdocs.cfg:</div><div style><br></div><div style><div>title: "SKM Documentation"</div><div>host: <a href="http://publican.vnf.lan">http://publican.vnf.lan</a></div>
<div>def_lang: en-US</div><div>web_style: 2</div></div><div><br></div><div style>- Tried to build Publican's "common" brand via:</div><div style><br></div><div style>$ cd /usr/share/publican/Common_Content/common (is this where it lives?)</div>
<div style>$ sudo publican build --formats=xml --langs=all --publish<br></div><div style><br></div><div style>This error'd with:</div><div style><br></div><div style>"Invalid build request: no PO files exist for language ar-SA at /usr/bin/publican line 921."</div>
<div style><br></div><div style>So I limited it to english which worked:</div><div style><br></div><div style>$ sudo publican build --formats=xml --langs=en-US --publish<br></div><div style>$ publican install_brand --web --path=/videonext/webdocs/html/docs</div>
<div style><br></div><div style>- Repeated the same with our brand:</div><div style><br></div><div style>$ cd /videonext/doc-3.7.0/brands/publican-videoNEXT</div><div style><div>$ publican build --formats=xml --langs=en-US --publish<br>
</div><div>$ publican install_brand --web --path=/videonext/webdocs/html/docs<br></div><div><br></div><div style>- Updated the web site:</div><div style><br></div><div>$ publican update_site --site_config /videonext/webdocs/webdocs.cfg</div>
</div><div style><br></div><div style>- Built and added our "home page" article and a sample book template (that uses videoNEXT brand):</div><div style><br></div><div style><div>$ cd /videonext/doc-3.7.0/documents/Home_Page</div>
<div>$ publican clean</div><div>$ publican build --publish --formats=html-single --embedtoc --langs=en-US </div><div>$ publican install_book --site_config /videonext/webdocs/webdocs.cfg --lang en-US</div><div>$ publican update_site --site_config /videonext/webdocs/webdocs.cfg</div>
<div><br></div></div><div style><div>$ cd /videonext/doc-3.7.0/templates/videoNEXT_Template</div><div>$ publican clean</div><div>$ publican build --publish --formats html,pdf,epub --embedtoc --langs=all</div><div>$ publican install_book --site_config /videonext/webdocs/webdocs.cfg --lang en-US</div>
<div>$ publican update_site --site_config /videonext/webdocs/webdocs.cfg</div><div><br></div><div><br></div><div style>At this point the web site home page is "visible" (and style 2 is nicer ;) ), although there are still a variety of 404's keeping it from being usable:</div>
<div style><br></div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/videoNEXT/en-US/images/title_logo.svg</span><span style="color:rgb(255,0,0);font-family:Menlo,monospace;font-size:11px;line-height:12px;white-space:pre-wrap"><br>
</span></div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/videoNEXT/en-US/images/image_left.png</span><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap"><br>
</span></div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/videoNEXT/en-US/images/image_right.png</span><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap"><br>
</span></div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/videoNEXT/en-US/css/menu.css</span></div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/common/en-US/css/menu.css</span><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap"><br>
</span></div><div style><div><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/en-US/carousel.html</span><br></div><div><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/en-US/toc.html</span></div>
</div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/common.css</span><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap"><br>
</span></div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/overrides.css</span><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap"><br>
</span></div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">/lang.css</span><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap"><br>
</span></div><div style><span style="color:rgb(0,0,0);font-family:Menlo,monospace;font-size:11px;white-space:pre-wrap">...</span></div><div style><span style="color:rgb(255,0,0);font-family:Menlo,monospace;font-size:11px;line-height:12px;white-space:pre-wrap"><br>
</span></div></div><div style>I'm assuming the "install_brand --web" steps aren't working for me and should be responsible for bringing in the /common/* and /videoNEXT/* brand items. However, when I run those commands, brand-named subdirectories are never created under my web doc root. </div>
<div style><br></div><div style>Sorry this is got so long, but I'm hoping there is some error in what I'm doing. Any hints or pointers as to where the process is failing me would be greatly appreciated. </div><div style>
<br></div><div style>Thanks...</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 16, 2013 at 7:27 PM, Jeff Fearn <span dir="ltr"><<a href="mailto:jfearn@redhat.com" target="_blank">jfearn@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 05/17/2013 11:08 AM, James Pooton wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On Thu, May 16, 2013 at 4:55 PM, Jeff Fearn <<a href="mailto:jfearn@redhat.com" target="_blank">jfearn@redhat.com</a>> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
<br>
--embedtoc basically means "build this to use in a publican web site". The<br>
website contains the missing content. It's done this way so that you can<br>
change the style on a web site without having to rebuild every book or<br>
replace a mass of files.<br>
<br>
</div><a href="http://jfearn.fedorapeople." target="_blank">http://jfearn.fedorapeople.</a>**<u></u>org/en-US/Publican/3.0/html/**<br>
Users_Guide/sect-Users_Guide-*<u></u>*Website.html<br>
<br>
<<a href="http://jfearn.fedorapeople.org/en-US/Publican/3.0/html/Users_Guide/sect-Users_Guide-Website.html" target="_blank">http://jfearn.fedorapeople.<u></u>org/en-US/Publican/3.0/html/<u></u>Users_Guide/sect-Users_Guide-<u></u>Website.html</a>><br>
</blockquote><div><div class="h5">
<br>
<br>
That's actually the page I was working through. :) I guess my question is<br>
this. That doc states:<br>
<br>
"The Publican-generated home page is the localizable page to which visitors<br>
are directed by the site JavaScript and which **provides the style** for<br>
the website structure."<br>
<br>
So I created a home page article per the directions, adding "web_type:<br>
home" and "brand: videoNEXT" to its publican.cfg. However, when building<br>
it for install, instructions ask for the following:<br>
<br>
publican build --publish --formats html-single --embedtoc --langs all<br>
<br>
Which results in HTML without any brand/style content applied, apparently<br>
because of the --embedtoc.(?) So installing this into the website doesn't<br>
seem to bring with our brand/style information. I'm sure I'm missing<br>
something simple here, but what part of the process supplies the<br>
brand/style css and (common_content) images to the web doc root? I was<br>
assuming it came with the home page article, or is it supposed to be<br>
manually gathered?<br>
<br>
To be clear, after going through the process of create_site, adding a home<br>
page article, and one other book. (both added to the web site). I can see<br>
the "content" from the home page and book doc when browsing, but there are<br>
lots of 404s as you'll see below:<br>
<br>
/common/en-US/css/menu.css<br>
/videoNEXT/en-US/css/menu.css<br>
/en-US/labels.js<br>
/footer.html<br>
/videoNEXT/en-US/images/image_<u></u>left.png<br>
/videoNEXT/en-US/images/image_<u></u>right.png<br>
/en-US/images/web_logo.png<br>
/common.css<br>
/overrides.css<br>
/lang.css<br>
</div></div></blockquote>
<br>
Gah! Looks like some steps are missing for changes introduced in 3.1.<br>
<br>
RPM sites:<br>
<br>
$ yum install publican-web publican-$brand-web<br>
$ publican update_site<br>
<br>
<br>
For manual sites:<br>
<br>
$ cd $brandsrc_dir (yes including the common brand in the publican source >_<)<br>
$ publican build --formats=xml --langs=all --publish # brands don't use embedtoc<br>
$ publican install_brand --web --path=$path_to_site_root_dir<br>
# repeat for all brands<br>
$ publican update_site --site_config $path_to_site_cfg<br>
<br>
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'.<br>
<br>
$ publican help_config | grep -A3 web_style<br>
web_style:<br>
Splash pages should be generated to be compatible with this web style. Valid values are 1 and 2.<br>
Default: 1<br>
Constraint: [1-2]<br>
<br>
Which is actually a pretty sad description given '2' is an entirely different web layout :-(<br>
<br>
Cheers, Jeff<div class="HOEnZb"><div class="h5"><br>
.<br>
-- <br>
Jeff Fearn <<a href="mailto:jfearn@redhat.com" target="_blank">jfearn@redhat.com</a>><br>
Senior Software Engineer<br>
Infrastructure Engineering & Development (AEU)<br>
Red Hat Asia Pacific Pty Ltd<br>
GPG: 0x0357E8F0<br>
<br>
______________________________<u></u>_________________<br>
publican-list mailing list<br>
<a href="mailto:publican-list@redhat.com" target="_blank">publican-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/publican-list" target="_blank">https://www.redhat.com/<u></u>mailman/listinfo/publican-list</a><br>
Wiki: <a href="https://fedorahosted.org/publican" target="_blank">https://fedorahosted.org/<u></u>publican</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><span style="border-collapse:collapse"><font color="#333333" face="arial, helvetica, sans-serif"><b>James Pooton</b></font></span><div><span style="border-collapse:collapse"><div>
<font face="arial, helvetica, sans-serif" color="#666666">Director, Software Development</font></div><div><font face="arial, helvetica, sans-serif">videoNEXT Federal Systems, Inc.<span style="border-collapse:collapse"><br>
<font color="#333333">571.485.2930 / cell</font></span><font color="#333333">: 571.314.3183</font></font></div></span></div>
</div>