I have quite a big resolution (1600x900) and I do not think that the header is too empty. I would rather be bothered by a not-used right margin.

I do not think that the landscape fits with the bright background as it is, maybe it should be brighter. The background looks really good, it is friendlier and warmer than the current one.

The introduction is already very well, you should maybe only put some non-breaking spaces like that: "Settlers I & II™ (© Bluebyte)". I do not like when the new line starts with "& II", but that is just for good-looking.

but that is just for good-looking

That's all what a new design is for, isn't it? I will change that.

I also don't really like it with the landscape. I will remove it until we either get a better image or decide to leave it empty.

Short summary of today changes:

• added non-breaking spaces (thanks wl-zocker)
• improved search form (placeholder text)
• changed doctype to HTML5; website is now valid HTML5 and CSS3
• fixed small bug in Internet Explorer 7

Some progress again: I now have a working copy of the website with the new design. It runs on another port on the same server: http://shevonar.ddns.info:8000. Currently only the main page works, everything else looks strange because I have not yet worked on it.

I also created a bazaar branch, so everyone in the widelands-dev team can and is invited to participate

Hey Shevonar ,

I have to say: the design was good before, but gets even better with almost every change you do. Very good work!

For all the others: the test website at http://shevonar.ddns.info:8000/ seems to be work in progress - I F5 the side every 20-60 minutes to check what has been changed lately

Concerning the newest changes: the integrated login box and the placeholder texts in the login boxes and the search box are great and give the possibility to have even less text in there without loss of functionality. However concerning this, I think there was a discussion about security when sending passwords between Janus and SirVer (or someone else??) - I am not quite sure, but I think they initially removed the integrated login box to ensure, that users switch to the https:// side for login to have a secure ssl connection for password transmission. The way it is now in your design would allow a http:// login request - personally I don't see a big problem there, but better try to ask one of them whether I remember the discussion correctly and whether an integrated login is useful. Maybe it would even be possible to put the whole side on https.

AND: Am I right, that the placeholder text for the password is not shown because it would show "****" anyways?

Keep on the good work!

I F5 the side every 20-60 minutes to check what has been changed lately

I have to learn for an exam and in learning pauses I work on the website

I see your point. It is no problem to remove the direct login again, but the extra click always annoyed me. Also on the current website Google Chrome complains about some "insecure resources" on the login site. A complete https:// website sounds like a nice solution.

AND: Am I right, that the placeholder text for the password is not shown because it would show "****" anyways?

A HTML5 placeholder would show "Password" but since I have to use javascript to get a placeholder-like behavior in older browsers the placeholder text is written into the password field and then it shows "********". But I think it is clear enough what you have to enter there

Putting the complete website under https will put a lot of strain on the server. That is why it wasn't done it is unwise to do it in the future.

Forget the most important thing: The new site looks gorgeous. I like the lighter background a lot.

So do you think I should remove the direct login form and only show a link to the https site? Or keep it as is? Or maybe put an additional link to the secure login for those who care?

You should add a direct link to the login page (like it is currently implemented). Leaving the users a choice is a bad idea: non technically inclined users will just login without any idea what the security risk is. And frankly: it should not be their problem.

The ideal solution would be to have the whole site also available on SSL, but as mentioned, our machine can't handle the load - it is already quite strained on memory.

Very nice work, Shenovar!

If you would put the SSH address directly in the form tag, (like facebook does), only a man-in-the-middle (http://en.wikipedia.org/wiki/Man-in-the-middle_attack) can get the password by modifying the normal http page, the password will be sent encrypted.

<form action="https://wl.widelands.org/..." ... >