Bug 1215846 - Lacks theming options
Summary: Lacks theming options
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Component-UI
Version: development
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Damian Jansen
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-28 00:29 UTC by Elizabeth K. Joseph
Modified: 2015-07-28 23:13 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-28 23:13:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Elizabeth K. Joseph 2015-04-28 00:29:57 UTC
Description of problem:

We're seeking to incorporate this into our infrastructure where most of our tools are themed to our project, but Zanata currently seems to lack theming options for the web UI. Having at least some build in customization options for CSS and logos would be great for tying it into everything else our developers and translators work with.

Comment 1 Luke Brooker 2015-05-18 02:54:54 UTC
At a fundamental level, this wouldn't be too hard to do if you wanted to manipulate the Sass/CSS manually, as all the colours in Zanata's assets are stored in variables that could be changed.

Some colours are used to convey certain meaning and should be kept similar to the original to keep the experience consistent.

To implement this properly, I'd like to add some basic options to the admin UI.

What types of customisations are you looking for in regards to CSS? Is just some colours in a few places and then the logo?

I'd like to do this tastefully so it looks purposeful and your branding fits with the current design.

Comment 2 Elizabeth K. Joseph 2015-05-22 21:03:31 UTC
I'd say something simple like logo and colors.

Some examples from elsewhere in our infrastructure:

A basic cgit: https://git.kernel.org/cgit

With our CSS+logo additions: http://git.openstack.org/cgit/

Our fear with doing it manually is diverging from upstream and would cause us to have to maintain CSS on our own. Being able to specify something like an additional CSS file and a logo other than default would be great.

Comment 3 Zanata Migrator 2015-07-28 23:13:33 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-69


Note You need to log in before you can comment on or make changes to this bug.