Changes between Initial Version and Version 1 of TracInterfaceCustomization


Ignore:
Timestamp:
04/23/10 16:58:29 (7 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracInterfaceCustomization

    v1 v1  
     1= Customizing the Trac Interface = 
     2[[TracGuideToc]] 
     3 
     4== Introduction == 
     5This page is meant to give users suggestions on how they can customize the look of Trac.  Topics on this page cover editing the HTML templates and CSS files, but not the program code itself.  The topics are intended to show users how they can modify the look of Trac to meet their specific needs.  Suggestions for changes to Trac's interface applicable to all users should be filed as tickets, not listed on this page. 
     6 
     7== Project Logo and Icon == 
     8The easiest parts of the Trac interface to customize are the logo and the site icon.  Both of these can be configured with settings in [wiki:TracIni trac.ini]. 
     9 
     10The logo or icon image should be put in a folder named "htdocs" in your project's environment folder.  (''Note: in projects created with a Trac version prior to 0.9 you will need to create this folder'') 
     11 
     12 ''Note: you can actually put the logo and icon anywhere on your server (as long as it's accessible through the web server), and use their absolute or server-relative URLs in the configuration.'' 
     13 
     14Now configure the appropriate section of your [wiki:TracIni trac.ini]: 
     15 
     16=== Logo === 
     17Change the `src` setting to `site/` followed by the name of your image file.  The `width` and `height` settings should be modified to match your image's dimensions (the Trac chrome handler uses "`site/`" for files within the project directory `htdocs` and "`common/`" for the common ones). 
     18 
     19{{{ 
     20[header_logo] 
     21src = site/my_logo.gif 
     22alt = My Project 
     23width = 300 
     24height = 100 
     25}}} 
     26 
     27=== Icon === 
     28Icons should be a 16x16 image in `.gif` or `.ico` format.  Change the `icon` setting to `site/` followed by the name of your icon file.  Icons will typically be displayed by your web browser next to the site's URL and in the `Bookmarks` menu. 
     29 
     30{{{ 
     31[project] 
     32icon = site/my_icon.ico 
     33}}} 
     34 
     35Note though that this icon is ignored by Internet Explorer, which only accepts a file named ``favicon.ico`` at the root of the host. To make the project icon work in both IE and other browsers, you can store the icon in the document root of the host, and reference it from ``trac.ini`` as follows: 
     36 
     37{{{ 
     38[project] 
     39icon = /favicon.ico 
     40}}} 
     41 
     42== Custom Navigation Entries == 
     43The new [mainnav] and [metanav] can now be used to customize the text and link used for the navigation items, or even to disable them (but not for adding new ones). 
     44 
     45In the following example, we rename the link to the Wiki start "Home", and hide the "Help/Guide". We also make the "View Tickets" entry link to a specific report . 
     46{{{ 
     47[mainnav] 
     48wiki.label = Home 
     49tickets.href = /report/24 
     50 
     51[metanav] 
     52help = disabled 
     53}}} 
     54 
     55See also TracNavigation for a more detailed explanation of the mainnav and metanav terms. 
     56 
     57== Site Appearance == 
     58 
     59Trac is using [http://genshi.edgewall.org Genshi] as the templating engine. Documentation is yet to be written, in the meantime the following tip should work. 
     60 
     61Say you want to add a link to a custom stylesheet, and then your own 
     62header and footer.  Create a file {{{/path/to/env/templates/site.html}}} or {{{/path/to/inherit/option/templates_dir/site.html}}}, with contents like this: 
     63 
     64{{{ 
     65#!xml 
     66<html xmlns="http://www.w3.org/1999/xhtml" 
     67      xmlns:py="http://genshi.edgewall.org/" 
     68      py:strip=""> 
     69 
     70  <!--! Add site-specific style sheet --> 
     71  <head py:match="head" py:attrs="select('@*')"> 
     72    ${select('*|comment()|text()')} 
     73    <link rel="stylesheet" type="text/css" 
     74          href="${href.chrome('site/style.css')}" /> 
     75  </head> 
     76 
     77  <body py:match="body" py:attrs="select('@*')"> 
     78    <!--! Add site-specific header --> 
     79    <div id="siteheader"> 
     80      <!--! Place your header content here... --> 
     81    </div> 
     82 
     83    ${select('*|text()')} 
     84 
     85    <!--! Add site-specific footer --> 
     86    <div id="sitefooter"> 
     87      <!--! Place your footer content here... --> 
     88    </div> 
     89  </body> 
     90</html> 
     91}}} 
     92Note that this references your environment's `htdocs/style.css`. 
     93 
     94Example snippet of adding introduction text to the new ticket form (hide when preview): 
     95 
     96{{{ 
     97#!xml 
     98<form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')"> 
     99  <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)"> 
     100    <p>Please make sure to search for existing tickets before reporting a new one!</p> 
     101  </py:if> 
     102  ${select('*')}  
     103</form> 
     104}}} 
     105 
     106If the environment is upgraded from 0.10 and a `site_newticket.cs` file already exists, it can actually be loaded by using a workaroud - providing it contains no ClearSilver processing. In addition, as only one element can be imported, the content needs some sort of wrapper such as a `<div>` block or other similar parent container. The XInclude namespace must be specified to allow includes, but that can be moved to document root along with the others: 
     107{{{ 
     108#!xml 
     109<form py:match="div[@id='content' and @class='ticket']/form" py:attrs="select('@*')" 
     110        xmlns:xi="http://www.w3.org/2001/XInclude"> 
     111  <py:if test="req.environ['PATH_INFO'] == '/newticket' and (not 'preview' in req.args)">  
     112    <xi:include href="site_newticket.cs"><xi:fallback /></xi:include> 
     113  </py:if> 
     114  ${select('*')}  
     115</form> 
     116}}} 
     117 
     118Also note that the `site.html` (despite its name) can be put in a common templates directory - see the `[inherit] templates_dir` option. This could provide easier maintainence (and a migration path from 0.10 for larger installations) as one new global `site.html` file can be made to include any existing header, footer and newticket snippets. 
     119 
     120== Project List == 
     121You can use a custom Genshi template to display the list of projects if you are using Trac with multiple projects.   
     122 
     123The following is the basic template used by Trac to display a list of links to the projects.  For projects that could not be loaded it displays an error message. You can use this as a starting point for your own index template. 
     124 
     125{{{ 
     126#!text/html 
     127<!DOCTYPE html 
     128    PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" 
     129    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 
     130<html xmlns="http://www.w3.org/1999/xhtml" 
     131      xmlns:py="http://genshi.edgewall.org/" 
     132      xmlns:xi="http://www.w3.org/2001/XInclude"> 
     133  <head> 
     134    <title>Available Projects</title> 
     135  </head> 
     136  <body> 
     137    <h1>Available Projects</h1> 
     138    <ul> 
     139      <li py:for="project in projects" py:choose=""> 
     140        <a py:when="project.href" href="$project.href" 
     141           title="$project.description">$project.name</a> 
     142        <py:otherwise> 
     143          <small>$project.name: <em>Error</em> <br /> ($project.description)</small> 
     144        </py:otherwise> 
     145      </li> 
     146    </ul> 
     147  </body> 
     148</html> 
     149}}} 
     150 
     151Once you've created your custom template you will need to configure the webserver to tell Trac where the template is located (pls verify ... not yet changed to 0.11): 
     152 
     153For [wiki:TracFastCgi FastCGI]: 
     154{{{ 
     155FastCgiConfig -initial-env TRAC_ENV_PARENT_DIR=/parent/dir/of/projects \ 
     156              -initial-env TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
     157}}} 
     158 
     159For [wiki:TracModPython mod_python]: 
     160{{{ 
     161PythonOption TracEnvIndexTemplate /path/to/template 
     162}}} 
     163 
     164For [wiki:TracCgi CGI]: 
     165{{{ 
     166SetEnv TRAC_ENV_INDEX_TEMPLATE /path/to/template 
     167}}} 
     168 
     169For [wiki:TracStandalone], you'll need to set up the `TRAC_ENV_INDEX_TEMPLATE` environment variable in the shell used to launch tracd: 
     170 - Unix 
     171   {{{ 
     172#!sh 
     173$ export TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
     174   }}} 
     175 - Windows 
     176   {{{ 
     177#!sh 
     178$ set TRAC_ENV_INDEX_TEMPLATE=/path/to/template 
     179   }}} 
     180 
     181---- 
     182See also TracGuide, TracIni