Bug 708877

Summary: Initial top-level nav page
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: Web-UIAssignee: Dana Mison <dmison>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: lcarlon, mcaspers, serogers, topic-tool-list
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-02 02:57:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 703365, 705623    

Description Joshua Wulf 2011-05-30 00:36:01 UTC 
We need a high-level navigation page. 

For the first cut, let's try this:

It's got tabs for the audiences. We'll use the Yahoo YUI 3 tabview initially: http://developer.yahoo.com/yui/3/tabview/

So we have audiences on tabs, and then on each tab we have a list of "Technologies" where we list all the technologies that have content, and a list of "Concerns" where we list all the concerns that have content for that audience. 

Each Technology list item is the name of the [Technology] with a link to the page "Audience > [Technology] by Concern"

Each Concern list item is the name of the [Concern] with a link to the page "Audience > [Concern] by Technology"

This should be generated in the docbook. We'll build it with publican, then rename it as index.html.
Comment 1 Sean Rogers 2011-05-31 06:48:35 UTC 
If we're "dog-fooding", here is the RichFaces tab view:
http://docs.jboss.org/richfaces/latest_4_0_X/Component_Reference/en-US/html/chap-Component_Reference-Panels.html#sect-Component_Reference-Panels-richtabPanel
Comment 2 Joshua Wulf 2011-05-31 11:11:29 UTC 
Can RichFaces be used with publican -> html + .css in a publican brand?

I think it requires server-side support. Our output is html + css served via Apache.
Comment 3 Joshua Wulf 2011-06-02 11:56:23 UTC 
*** Bug 707804 has been marked as a duplicate of this bug. ***
Comment 4 Matthew Casperson 2011-06-09 02:25:10 UTC 
Here is a sample of the output for a top-level nav page. The <para role="AudienceNavLinksRole"> element contains the links that would become tabs. The <para role="Developer-Technologies"> element contains the links for Developer Technologies, while the <para role="Developer-Concerns"> elements contains the links for the Developer Concerns (replace Developer with Administrator or Migration in the role attribute depending on what top-level page you are looking at).

Using the roles it should be possible to transform these elements into tabs and columns.

<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Book.ent">
%BOOK_ENTITIES;
]>

<chapter id="Developer">
<title>Developer</title>
<para role="AudienceNavLinksRole">
<itemizedlist>
<listitem><para><link linkend="Developer">Developer</link></para></listitem>
<listitem><para><link linkend="Administrator">Administrator</link></para></listitem>
<listitem><para><link linkend="Migration">Migration</link></para></listitem>
</itemizedlist>
</para><para role="Developer-Technologies">
<itemizedlist>
<listitem><para><link linkend="NavPageXRef-tag2-tag69-cat2">Application Server</link></para></listitem>
</itemizedlist>
</para><para role="Developer-Concerns">
<itemizedlist>
<listitem><para><link linkend="NavPageXRef-tag2-tag95-cat3">App Deployment</link></para></listitem>
<listitem><para><link linkend="NavPageXRef-tag2-tag53-cat3">Application Development</link></para></listitem>
<listitem><para><link linkend="NavPageXRef-tag2-tag60-cat3">Installation</link></para></listitem>
<listitem><para><link linkend="NavPageXRef-tag2-tag85-cat3">Getting Started</link></para></listitem>
</itemizedlist>
</para>
</chapter>
Comment 5 Matthew Casperson 2011-08-02 02:57:26 UTC 
These nav pages have been superseded by a treeview.