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.

Currently does not install (missing the images directory). Testing on hold until Jonathan has had a chance to fix. 

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, except for the difficulty in getting the package to install correctly.  

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

PASS. Final product ideally should not have the version number in the name to make it more easily installable by new users. What's this file: andreas01empty.pt? I find it a little strange that your main.css is in the browser directory instead of in the skins folder. I'm also in favor of not having empty stylesheets to override base Plone stylesheets -- removing them via the stylesheets.xml would probably be a little cleaner. Consolidate if you can. 

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

N/A 

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

ISSUE: main.css does not currently support DTML calls. We should probably try to support DTML, even if you don't use it in the theme itself. It's more for users to be able to tweak your theme after the fact. You can pull the appropriate lines of code for this from a 2.5 ploneCustom.css file. Also, if you do that, make sure your css files at called main.css.dtml  instead of just main.css.  

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). 

ISSUE: Site needs a readme.doc. Check the simplicity theme for an example of what might belong there.  

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.

ISSUE / FAIL: The site has only been tested on Safari and Firefox for Mac [edit: sssemone: also tested under IE7 and Firefox under XP SP2 against Plone 3.1.1 with the same results noted].  Right column needs to be sized appropriately so that the footer can fit. The contents view is hard to read without any borders in place. h1, h2, h3 headers should be in blue, not black. Portlet headers should be grey. Pullquote and callout styles don't really do much. I was expecting something like what you see in the content well here, where it says "posted": http://s.themes.wordpress.net/snapshots/704-big.jpg

Need to bring back the site actions, even though they're not part of the original Andreas01 theme. 

Please bring back the site search and verify that LiveSearch works as it should. 

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

PASS. For the most part, it works fine without these specified. 

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

PASS. It works, but looks a little too much like base Plone for my taste (rollovers). 

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

ISSUE: Needs a little reformatting in there so that the Add on Product Configuration doesn't get broken. 

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. 

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. Not included. 

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

I think it will, once the right column is sized correctly. 

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. 

18) A site with this theme prints properly. 

Not tested, I don't have access to a printer.  

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.