Opened 9 years ago

Last modified 6 months ago

#1105 new task

un-red the trac theme

Reported by: hamish Owned by: grass-dev@…
Priority: minor Milestone: Website
Component: Website Version:
Keywords: trac theme Cc:
CPU: Unspecified Platform: Unspecified

Description

hi,

the gratuitous use of red may be great for National Geographic Kodachrome photography, but in the trac pages it makes my eyes hurt. Any chance to switch it back to something less intense?

seems fairly easy:

http://trac.edgewall.org/wiki/CookBook/SiteStyleCss

thanks, Hamish

Change History (8)

comment:1 Changed 9 years ago by neteler

Which red do you mean?

Markus

comment:3 Changed 6 years ago by hamish

an example of a nicely themed trac:

http://eden.sahanafoundation.org/timeline

comment:4 Changed 6 years ago by lucadelu

another one is zoo-project

http://www.zoo-project.org/trac/

I could ask to zoo-tribe if someone would like to help us....

comment:5 Changed 3 years ago by Nikos Alexandris

If efforts will be taken in improving the color scheme, then le it be a unified color scheme for trac, wiki and the Programmer's manual as well. See also #3146.

comment:6 Changed 3 years ago by neteler

I wonder where to insert style changes:

/var/www/trac/grass/templates/site_css.cs

is empty. No other css file on the server...

comment:7 in reply to:  6 Changed 3 years ago by Nikos Alexandris

Replying to neteler:

I wonder where to insert style changes: /var/www/trac/grass/templates/site_css.cs is empty. No other css file on the server...

See https://trac.edgewall.org/wiki/TracInterfaceCustomization#SiteAppearance

Also, useful notes lower down in the https://trac.edgewall.org/wiki/TracInterfaceCustomization#ProjectTemplates section:

The appearance of each individual Trac environment, ie instance of a project, can be customized independently of other projects, even those hosted on the same server. The recommended way is to use a site.html template whenever possible, see #SiteAppearance. Using site.html means changes are made to the original templates as they are rendered, and you should not normally need to redo modifications whenever Trac is upgraded. If you do make a copy of theme.html or any other Trac template, you need to migrate your modifiations to the newer version. If not, new Trac features or bug fixes may not work as expected.

comment:8 Changed 6 months ago by sbl

Still relevant? Also after move to git?

Note: See TracTickets for help on using tickets.