Verify the following:

Please note PASS / FAIL / ISSUE on each of the following. If there are errors, state platform, browser, version and give information to reproduce the issue. Since there will likely be multiple testers, please put your name / nick next to your comments.

1) If the site is installed with other themes / products, it does not "bonk" the other sites. Look for elements of the design that might try to override other products in your site. We are looking to make sure that the IThemeSpecific interface is being used correctly here.

PASS.

2) The theme can be installed easily and without requiring tweaks in the ZMI. All generic setup items should be covered via the files in the profiles directory.

PASS.

3) The theme follows all new Zope3 conventions -- naming, file structure, etc. The site is created using ZopeSkel.

PASS. Is there a reason you have a separate directory for images_red? Seems like they would belong under custom_images. I'd consider getting rid of some of the extraneous things you don't use, such as main.css.

duffyd: Reason for the extraneous directory was that this is what comes with the theme and I suppose I wanted to try and keep true to the original theme filenames/directories/etc. On reflection, this isn't really important so I'll make the changes you specify - thanks!

duffyd: Made changes as per Veda's suggestion.

4) Any required javascripts or additional CSS are registered correctly.

PASS.

5) New stylesheets have the requisite code in place to accept DTML calls (so that base properties can be used).

I think you're missing the full call here. I usually use both of these:

/* <dtml-with base_properties> (do not remove this :) */

/* <dtml-call "REQUEST.set('portal_url', portal_url())"> (not this either :) */

duffyd: Made changes as per Veda's suggestion.

6) The skin layers in the default theme list in the correct order. (Not sure how much of this we can really control).

PASS.

7) The readme states the name of the author, contact information, compatible versions, and any product dependencies (ie, for tableless).

PROBABLY SHOULD POPULATE YOUR README. SEE SIMPLICITY THEME FOR IDEAS.

duffyd: Made changes as per Veda's suggestion.

8) The theme plays well in all of the "A" list of supported browsers: http://developer.yahoo.com/yui/articles/gbs/index.html excluding Windows98. Look for rollovers, CSS changes that might have been forgotten. Feel free to test additional media.

Plays well in Safari and Mac. Not tested against IE.

When adding a new portlet, it is VERY hard to see the fields for adding title, etc.

duffyd: Have upped the contrast on the borders slightly (hopefully good enough).

Global logo isn't clickable to get back to home.

duffyd: Now clickable.

Calendar still has some styles inherent to base plone (norwegian blue).

Please bring back the search field (remember to test your LiveSearch).

duffyd: Fixed up the Calendar CSS and the search portlet.

ssemone here doing a bit of browser testing:

• I note that in IE7 under XP SP2 that there is an artifact "bleed through" of the calendar portlet when editing a page in kupu full screen. See screen shot below:

duffyd: Removed fullscreen action as couldn't get to function in IE6/7. 

• Strange portlet behavior under Firefox 2.0.0.14 in XP SP2 and OS X 10.5.2. This is when logged in and viewing a page that has portlets:

duffyd: Couldn't replicate this behaviour as don't have copy of FF running on WinXP/OSX.

9) The stylesheets implement base styles for items like .portlet, .portletItem, etc. to handle cases where users add new portlets.

PASS.

10) The site map works and is consistent with the rest of the theme.

Is there a reason why you've hidden sitemap, site setup, etc.? Also, I would remove some of the borders and mouseovers that you see on the sitemap. Looks like base Plone.

duffyd: Put back site actions and have hidden mouseovers in sitemap.

11) The admin area works and is consistent with the rest of the theme.

PASS.

12) When adding related items, the text is readable on the popup window. Usually, this is only a problem for themes with dark backgrounds; additional styles might be needed.

N/A. NOT AVAILABLE IN 3.0.

13) If there are custom content types (there probably won't be), verify that an icon has been specified for the drop down list.

N/A.

14) A favicon has been included with the theme. Not required, but would be nice.

N/A.

15) The site plays well with enlarged fonts (accessibility).

PASS.

16) The site can be adapted to other languages easily (ie, images are not used for menu items, etc.)

PASS.

17) Main template changes are kept to a minimum. If the main template has been changed, it should be called out in a TAL comment.

PASS. When do you use prefs_main_template?

duffyd: This was included in the plone-tableless product skin (just copied the whole skin).

duffyd: Removed prefs_main_template.

18) A site with this theme prints properly.

NOT TESTED.

19) The site should play well with the presentation styles. This is the "presentation mode" you see when you first install Plone 3.0.

PASS. Looks like base Plone.