It's now been a week since I asked you to test the new-look Brickset and provide feedback. So far 700 of you have done so which is fantastic, thank you.
I've read all of it and have attended to many of the bug reports and, as you will notice if you take another look now, added a couple of the most-missed features. The 'new in the database' and 'new at shop.LEGO.com' lists are back, in the sidebar. I've also created another view for set listings, 'classic', which looks similar to that on the current site.
As for the header font that many of you commented on, it seemed that Google Chrome was particularly bad at rendering it. After some investigation, I found a fix (encourage Chrome to use the SVG version) which has made a vast difference and, to my eyes at least, the text is now clear and crisp and how the designer intended. There are a couple of minor issues to resolve which the fix has introduced (like the position of the icons in the menu blocks) which I'll be sorting out soon.
I was also encouraged by the fact that around 400 people were using the site at one point and it didn't crash or kill the database. Load-testing the site is not really possible (on a small budget, at least) until you actually get lots of people to use it, so I am now confident that it will withstand normal levels of traffic when it goes live.
Several people have commented about strange layout problems, text overlapping and that sort of thing. I've never seen anything like that when I've been testing so can't therefore do much about it. If you are experiencing problems like that, please send me screenshots (huw at brickset.com) and LMK what browser and operating system you're using. I can't promise to fix them but at least I'll get an idea what the problem is.
So, please, keep the feedback coming and if the bug you reported is still evident, feel free to email me with details or post something in the comments.
If you're wondering about the prizes I promised, I'll continue to accept entries until next weekend, then make the draw shortly afterwards.
Commenting has ended on this article.