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-31. (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.
• Splitting of information may be done just by creating a wiki index of user pages. Splitting of TOC macro will hide the developer documentation, but not sure if needed.

Related

​http://trac-hacks.org/wiki/theme contains themes for trac.
​http://trac-hacks.org/wiki/ConsultantTheme looks most promising.
​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/TwikiPatternSkinTheme

How to demo

Present diagrams, links of designs that are apllicable, explain your proposal on dividing information. This task should leave only the technical part of the site to be done.

Design

Discussed the separation of the site with team leader. New design was brought for the user site and it was decided to extend it for the track, witch became developers side of the site.

Implementation

The Sophie 2 home page could be found on this locations: ​http://www.sophiecommons.org ​http://www.sophie-commons.org ​http://www.sophiecommunity.org ​http://www.sophie-community.org ​http://www.sophieproject.org

However they contain only the landing page. The users part of the site is http://sophie2.org/users and the developers site is http://sophie2.org/track

Testing

General:

1. The site should be centered within the browser window. Currently it

is anchored to the right.

2. As I'm sure you are aware, not all pages have been reskinned with

the new design (ie. the development section and user documentation).

Home:

1. If the page is resized, currently the top (logo and image collage)

and bottom portions (touts) of the site separate. They should be locked together at all times.

2. Probably related to the comment above, the two touts at the bottom

of the page aren't lining up correctly. The lower right tout box should align left with the "r" in "rich media" above.

User Home:

1. The main content box should be shorter (moving the author and

reader icons up) because there is not much content on the page. The content box should expand and contract depending on content length.

2. There should be space between the Download Sophie and Feature

Release Schedule sidebar touts. Please reference attached PDF and provided PSD.

3. A faint blue line should be placed above the footer links. This is

currently included on the Users > Downloads page.

Users > Downloads:

1. We planned for this page to be two columns (please see PDF or

provided PSD). Is this not possible in Trac? We feel that would allow the content to be more easily digested and read.

Comments

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