Edgewall Software

Opened 19 years ago

Closed 19 years ago

Last modified 16 years ago

#332 closed enhancement (fixed)

Custom header/footer templates and CSS for custom layouts

Reported by: anonymous Owned by: daniel
Priority: normal Milestone: 0.7
Component: general Version: 0.6.1
Severity: normal Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Matthew Good)

On the projects.edgewall.com trac installation you have a left menu bar. Is this a feature of trac? Is it done with the clearsilver templates? If not (or even if so) I would like to see this as a feature of trac:

Allow customization of the 'navigation' areas (header, footer, left) through trac rather than using the templates.

Attachments (0)

Change History (9)

comment:1 by daniel, 19 years ago

Milestone: 0.7.1
Summary: Left navigation barCustom header/footer templates and CSS for custom layouts

This is something we've been discussing earlier, and somehow never made it into a ticket.

On projects.edgewall.com we right now have a patch for the actual templates, applied automatically when we update it. This is of course far from optimal.

The most common request is being able to add Trac to an existing layout.

The case boils down to:

  • header.cs should include a site_header.cs at the top
  • footer.cs should include a site_footer.cs at the bottom
  • site_* should reside in the Environment, preferrably in <projenv>/templates/
  • <projenv>/templates/ should contain empty defaults and a README with a description
  • header.cs should include a site.css after all 'system' styles, to allow custom overrides.
  • site.css should probably reside in the Environment.

comment:2 by cmlenz@…, 19 years ago

I would suggest to include site_header.cs directly before the header div (which contains the Trac logo), and include site_footer.cs directly before the closing <body> tag (and thus after the footer div).

I agree that this approach, combined with a CSS customization layer that still needs to be worked out*, would indeed solve 99% of the integration requirements.

comment:3 by daniel, 19 years ago

Owner: changed from Jonas Borgström to daniel
Status: newassigned

comment:4 by daniel, 19 years ago

Exactly, and the remaining 1% is typically solved by editing the actual Trac templates themselves.

The level of complexity to support any simpler customization options is hardly worth an effort that better spent elsewhere. :)

comment:5 by daniel, 19 years ago

This is simple enough to add to 0.7 even, if only to make our own project website easier to maintain :-P

comment:6 by daniel, 19 years ago

Resolution: fixed
Status: assignedclosed

Added in [522].

comment:7 by anonymous, 16 years ago

Component: generalroadmap
Type: enhancementdefect

comment:8 by anonymous, 16 years ago

Component: roadmapgeneral

comment:9 by Matthew Good, 16 years ago

Description: modified (diff)
Type: defectenhancement

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain daniel.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from daniel to the specified user.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.