Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=SCS_SITE_DESIGN_R2, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

This revision should suggest clear proposals for the design of the community site.

Task requirements

• Watch the video taken on 2009-01-39. (The community site discussions)
• Dig for the presentation files (ask for them)
• Consider uploading them here (synchronize this one with the team leader)
• Research other trac sites, see their design for good ideas on reorganizing (related section)
• Suggest improvements
  • At least 2-3 different designs
  • Diagrams of these
  • A clear explanation of how to apply these to trac
• Think of ways to split the community site in developers and user parts
• Document results of your research
• Discuss on a meeting or with the team leader applying the design (actual applying is not part of this task)

Task result

Sample designs satisfying client requirements.

Implementation idea

Research trac themes as they seem to be the easiest customization option. Link in related section.

Related

​http://trac-hacks.org/wiki/theme contains themes for trac.
​http://ortus.svnrepository.com/coldbox/trac.cgi - provides a good example of dividing user documentation. Also the look is pleasant.
​http://trac-hacks.org/wiki/MoveableTypeTheme contains layout similar to our goal.
​http://trac-hacks.org/wiki/PyDotOrgTheme layout similar to our goal. ​http://trac-hacks.org/wiki/ConsultantTheme looks very promising.

How to demo

^{(Provide instructions for demonstration of the task.)}

Design

^{(Describe your design here.)}

Implementation

^{(Describe and link the implementation results here (from the wiki or the repository).)}

Testing

^{(Place the testing results here.)}

Comments

^{(Write comments for this or later revisions here.)}