Edgewall Software
Modify

Ticket #332 (closed enhancement: fixed)

Opened 8 years ago

Last modified 6 years ago

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:
Release Notes:
API Changes:

Description (last modified by mgood) (diff)

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

Change History

comment:1 Changed 8 years ago by daniel

  • Milestone set to 0.7.1
  • Summary changed from Left navigation bar to Custom 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 Changed 8 years ago by cmlenz@…

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 Changed 8 years ago by daniel

  • Milestone changed from 0.7.1 to 0.7
  • Owner changed from jonas to daniel
  • Status changed from new to assigned

comment:4 Changed 8 years ago by daniel

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 Changed 8 years ago by daniel

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

comment:6 Changed 8 years ago by daniel

  • Resolution set to fixed
  • Status changed from assigned to closed

Added in [522].

comment:7 Changed 6 years ago by anonymous

  • Component changed from general to roadmap
  • Type changed from enhancement to defect

comment:8 Changed 6 years ago by anonymous

  • Component changed from roadmap to general

comment:9 Changed 6 years ago by mgood

  • Description modified (diff)
  • Type changed from defect to enhancement
View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
to The owner will be changed from daniel. Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.