MozillaZine

Site Suggestions

Tuesday January 8th, 2002

A few of you have asked for us to post a news item taking your suggestions for the site, so here it is. Tell us all your ideas for what we can do to improve the site. Anything you want we'll think about, but try to keep it realistic.

Just to keep you updated, one of the things we're planning on working on is getting the ChromeZone up again, if we can find some volunteer editors to help organize themes. If you're interested, please email me and I'll get back to you sometime this week.

UPDATE! Right now we're working on dumping all the tables and other old HTML within the site to both show off Mozilla's skills, and to get our file sizes smaller. If you're using Communicator to view the site, you'll notice everything looking pretty ugly, thanks to the poor CSS support it offers. If you're using IE, it'll look a bit better, but thanks to IE's lacking CSS2 support, the sidebar will show up incorrectly. We've completely redone the homepage and talkback code, and we'll be working on the forums next.

UPDATE 2! We discovered Google's great "Search Site" feature, and have added it. Right now it has most areas of the site indexed except news item talkback pages. It will start indexing talkback today, and will hopefully add all of the old items, in addition to picking up the new ones.

UPDATE 3! We've been working hard to get as many of your suggestions as possible implemented, and we encourage you to continue the feedback. You can check this article's responses for what items we have fixed, or are working on.


#8 Quite a few thoughts....

by orev

Wednesday January 9th, 2002 7:50 AM

You are replying to this message

- to reduce bandwidth consumption, gzip everything and use the gz content encoding. Mozilla can handle this, and I think IE can too. It might even be something the web server can negotiate and do on the fly for you.

- The greatest resource of this site is the ability to know about the latest build. It would be great if we could vote up and down each daily build, so we don't actually have to wait for comments to be posted.

- also on the build comments, the recent addition of the "all bugs fixed since last update" is extremely valuable. If it could be "all bugs fixed since yesterday", and then the date just be updated automatically, it would reduce the load on the person who's actually writing the build bar comments.

- also, as you mentionned, removing lots of extraneous tables and going to almost pure CSS for formatting. NS4 is 6 years old now, it's time to move on.