[jboss-jira] [JBoss JIRA] (WFLY-1442) Web console branding across community and product versions

[Catherine Robson (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780280#comment-12780280 ] 

Catherine Robson commented on WFLY-1442:
----------------------------------------

>From Matt Carrano:

Hi Heiko,

We did talk about this yesterday.  The requirement is to keep the product logotype as a bitmap graphic to ensure the correct text styling is applied (it needs to use the Interstate font for RedHat product branding).  We will be working with brand to create a streamlined process for generating these when they are needed.  We were also wondering about the need for the version number in the product name.  This is not consistent with other products.

We are glad to work with you to generate any graphics you need.  Let me know if you see any concerns with this.

Regards,

Matt
                
> Web console branding across community and product versions 
> -----------------------------------------------------------
>
>                 Key: WFLY-1442
>                 URL: https://issues.jboss.org/browse/WFLY-1442
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Web Console
>            Reporter: Harald Pehl
>            Assignee: Harald Pehl
>
> Define a way to specify the branding for the web console across different community and product versions. The name and version used for the branding should be read from the {{product-name}} and {{product-version}} attributes of the root DMR resource. Regarding the logo there are different options:
> # Use a unique logo for the web console across all community and products / versions
> # Choose between a community (WildFly) and a product logo (RedHat)
> # Hold up all logos for any community / product version in the HAL release stream and choose dynamically.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira