Slashdot Mirror
FreeBSD Project Launches New Website
UltimaGuy writes "The FreeBSD Project has launched a new website today. The new design was created by Emily Boyd, a student at Smith College that they had the pleasure of working with through Google's Summer of Code program. The old website is also still available."
The problem for us blind old coots is finding the large stylesheet. Maybe they should default to large and let you whippersnappers choose the tiny stylesheet.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
I must admit, it makes it look more like they're providing a serious product rather than something made by a group of hippies and slackers.
*dives under a table with his Powerbook*
Direct away from face when opening.
I posted this yesterday
:)
( " The New FreeBSD Website is UP Thursday October 06, @06:15AM Rejected" )
as news only to be rejected. I dont know why it was rejected so i cant complain i was treated unfairly. But when someone posts news and is rejected then the news appears a day later posted by someone else. It makes me wonder what the fsck is going on round here.
On the topic. The new design is a major improvement, much nicer to look at, and hopefuly it can get carried through to a HTML version of the Handbook some time soon. that could do with a style overhaul, just to make reading the thing online nicer
XML - A clever joke would be here if
The old site packed a lot of information in without sucking, which is justification for admiration in itself. The new ones is in fact a bit better on this account (in my opinion). It looks a lot better, and I understand that this is important in a world where many people don't have the time or skill to look at things more than skin deep. However, this in itself doesn't impress me much. There are a lot of good designers out there (and a lot of bad ones to be sure); it isn't hard to make things look whizzy. What's nice is that substance and organization don't take a backseat the pizzaz, resulting in solid and usable design.
I had this discussion about this with one of the junior guys at work the other day. He was holding forth on how the web was really about information content, and sites should emphasize text, data and organization. I said, hold on. Should a web site for a movie or video game be text-centric? Or one proselytizing for a religion, or promoting a rock band? Web sites don't have to content-centric or text-centric, any more than books all need to be dictionaries. They do have to have a purpose, to accomplish certain goals. They are software. They have to variously allow the user to accomplish certain goals, or in some cases produce a kind of experience. One side or the other of this dichotomy may predominate, but there's nothing wrong with a reference site that looks impressive, or an entertainment site that also informs.
The old and new sites both get high marks for usability and organization, based on how I use this kind of site.Genreally, when I go to a software project's site, I'm in one of two modes:
First Time Mode:
(1) What does this thing do?
(2) How does it stack up against other projects/products in a similar space?
(3) What is required to run this?
(4) How do I obtain (buy/download) this software? How do I install it?
(5) Who is the organization behind this? Will it be there in six months? Can I get a hold of somebody if necessary?
(6) Where are the training and support materials?
(7) What are the differences between the various versions?
(8) What are other people saying about this? Is there evidence of mindshare?
Return Mode:
(1) What has changed in the product since my last visit? How are the various releases different? How have hardware requirements changed?
(2) Are there security or high priority bug fixes?
(3) What has changed in the support/documentation?
(4) Where do I get the software if I haven't installed it, or upgrade it if I have?
(5) Does the project show evidence of continued development and ongoing mindshare?
In both these modes both the old and new sites are very good for my purposes. The new one is definitely more "professional" looking, which is to say it looks a bit less like an open source project site and a bit more like a commercial software site, only not as brain dead.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
I am not sure whether the new headline on the homepage is a very wise and professional move of the FreeBSD project.
gopher://cramer.plaintext.cc http://cramer.plaintext.cc:70
Hopefully they will give the handbook a bit of a spring clean next...
Are you volunteering? The FreeBSD Documentation Project is always on the look out for new blood.
A Government Is a Body of People, Usually Notably Ungoverned
Ok, it needed some improvements, and also a lot may be because I'm used to it, but overall, I preferred the old site.
For a start, it made full use of my browsers screen size (the new site only uses a quarter of my browsers window.. damn 'fixed sized' web sites)
It also (and maybe as a consequence) squashes too much into a small space.
The news/upcoming events/in the media/security advisories sections now have too much prominence. Sure, this may be handy for 'regulars', but regulars know where to look anyway.
Surely, the purpose is to grab -- and keep -- new visitors to FreeBSD. As such, this large section merely confuses.
But, ultimately, I resent this page being squashed into a quarter of my window!!
Sig out of date
She has some nice OSS designes under her belt. A Google search shows she designed the pgsql site, for one. Her designes are attractive, but not as accessible as I would like. For example, most of her fonts are below 1em (1em being the size you tell your browser that you want). It is fine to go less than 1em for things such as copyright notices and advisory feeds and whatnot, but the majority of the text on the site should always be 1em: the user should have his say on what the font size is. I would also prefer more of my monitor real estate be used. I'm not a fan of squashed designes. Overall, everything is an improvement on the eyesore that was the status quo.
$ whatis themeaningoflife
themeaningoflife: not found
How else will you persist a stylesheet selection over multiple pages*?
Without the cookie or javascript you will just get the default stylesheet each time and you will have to change it on every page you go to.
* Yes, you can store it at the server end, with a lot of hassle. I don't think this is an ideal solution.