Bug 704776

Summary:	Style the topic output based on the topic lifecycle (Topic Lifestyle)
Product:	[Community] PressGang CCMS	Reporter:	Joshua Wulf <jwulf>
Component:	Web-UI	Assignee:	Joshua Wulf <jwulf>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	lcarlon, 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:	2012-02-03 07:25:07 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:	704777, 704778
Bug Blocks:

Description Joshua Wulf 2011-05-14 20:54:32 UTC

By giving the topic's root <section> element a "role" attribute, an html div class will be generated on output.

There can be two EAP6 brand packages for publican. One, the development one, styles the output html based on the lifestyle div, to visually communicate the topic's lifecycle phase. The other, the production one, does not visually alter the output based on this attribute.

The difference between the two, of course, is in the css.

Comment 1 Joshua Wulf 2011-05-23 04:12:35 UTC

OK, it's pretty easy to do - just need to figure out the best visual vocabulary to use. 


In the overrides.css for the brand do the following:

.IAProposed{
        background-color: #c2bfbf;
}

That one, for example, makes the background of IA_PROPOSED content grey.