GNOME Bugzilla – Bug 630114
website facelift
Last modified: 2011-12-02 22:17:08 UTC
I feel I do not express my gratitude towards this project enough. Gnumeric is awesome. It is lightweight, powerful, elegant. The Gnumeric website looks okay, but has a slightly outdated look. I think a small facelift would make the project more attractive. I could write a new stylesheet for it, just to harmonize the colors a bit (do you have an official color palette?), tweak the fonts (ex: Sans serif, dropshadows where appropriate...), update the screenshots, add the logo, etc. Or, if you want, a complete redesign is also possible, but that's more invasive and the current website does an okay/good job at making the contents easy to find. Would you folks be interested, or rather not?
I agree that the Gnumeric web site could definitely use an update, but you definitely need to talk with Morten about that. I don't even know how to get to the source of the site.
I wouldn't mind seeing an update. The source is in the gnomeweb-wml module under projects.gnome.org/gnumeric Git requires you to check you the whole thing which is about 500M.
Created attachment 172316 [details] screenshot Here is my first attempt at it. It's just some adjustments to the CSS and a couple of nonintrusive tweaks to the header (so it should work with the existing website code). I think this would probably be enough, unless you want a full redesign or code cleanup.
Interesting. I have been staring at it for a few minutes and a few things stand out: * The rounded corners of the headers look nice. The bigger size probably is good too. * But the "download sample" part got too close. * The space between the boxes on the left has the same colours as the rest of the page. That isn't new, but with the new colours, the contrast is higher and the spaces steal attention. I have no idea what the solution is. * I have always wanted if we want the colon in "Download:" etc. Again, not new, but is it right? * What kind of mouse-over effects are there?
> But the "download sample" part got too close. Oh yeah, I didn't pay enough attention to detail :) putting that thing in a floating div (if it isn't already) and adding a 10px margin should solve the problem quite easily. > The space between the boxes on the left has the same colours as the > rest of the page. That isn't new, but with the new colours, the > contrast is higher and the spaces steal attention. I have no idea > what the solution is. You mean the "blank" spaces between the menu boxes? I guess we could remove them and make the menu one big solid chunk (with the "headers" having a different background color). I haven't paid attention to the menu's border colors too, because I was a bit lazy and simply wanted to get a prototype out. > I have always wanted if we want the colon in "Download:" etc. Again, > not new, but is it right? I agree 100%. I would remove the ":" characters in the menu headers. > What kind of mouse-over effects are there? The same as before (I didn't pay much attention to those yet, to be honest).
Personally I am wondering why there are boxes on the left in the first place rather than just the text items (in a non-black colour) on the regular page background colour.
Well, maybe the whole thing could be replaced by a dropdown menu and put at the top, while we're at it... but this would pretty much mean a more invasive redesign.
Silly question: what's with the use of those <!--#echo var="rootdir" --> all over the place in the website's code, isn't it a bit redundant/optional?
Created attachment 175694 [details] [review] patch Here is a proper git patch for the changes I did in comment #3... should be better than nothing. The problem is that I don't have access to a server that has SSI to parse those .shtml files, so I can't work on it further (unless you have some corner on the web where I could do the required experimenting/testing).
> Silly question: what's with the use of those <!--#echo var="rootdir" --> all > over the place in the website's code, isn't it a bit redundant/optional? It's redundant in a file at top level, but not in a subdirectory where a sequence of ".." components would be needed.
The patch has been submitted. I am closing this bug since in a way it is much too generic. Unfortunately I have no server you could access to test with those shtml files.