HashOver 2.0 default theme: Second Draft
I closed the first draft issue, now it's time for a second draft.
Things to keep in mind about the default theme are:
- It should be minimal.
- It should be easy to understand.
- It should be as backwards compatible as possible.
- It should adjust well to both various screen and layout sizes
- It should adjust well to different settings, such as:
- Disabled avatars.
- Different font sizes.
- Elements in multiple places.
- Etc.
Any and all ideas, suggestions, recommendations, concerns, and contributions are welcomed and will be considered for inclusion into either the default theme or as an optional secondary theme.
Ideas so far...
Underlined inputs.

Dark/defined headers and buttons, dates in headers, likes/dislikes icons, and no rounding.
Credit where credit due: @Lux-Delux
A suggestion/idea: I think some less computer literate users would be confused to see login fields. They might think "I don't have an account here, what do I put?". I would suggest having a name, email, and website field only (marked as optional if optional), and then having the login button reveal fields to login. I'd also suggest moving it to the top right to group it with the input fields...either a user is going to enter info manually, or login to pull that info in.
Just my $.02
I completely understand that perception. Trying to find the right way to convey what is expected from the user and what the password and login fields do, has been something I've struggled with. My latest idea is to put an open lock icon on the end of the name field, clicking it would close the lock and reveal the password field, and perhaps a small message explaining what giving a password does.
It's tricky.
I would disable the password field and the login button by default, it's very confusing for users and I don't find it very useful.
I like the idea of "Underlined inputs". The screenshot show a very minimalistic theme that can be customizable just changing a few colors.
I would disable the password field and the login button by default, it's very confusing for users and I don't find it very useful.
Ah yes, this is a problem that still needs to be solved. Basically, that login is there so users can "log back in" to regain access to edit or delete their comments after their cookies expire. By default, this feature should probably not be presented as a login, and it shouldn't give the impression that it is a required login or that the user needs an account, but it is something many people find useful.
That said, actual logins are easy to implement, and I know of a few people who have done so, having that login button there serves those folks well. How it works now is basically a middle ground between actual logins and the "remember what you last posted with" behaviors.
It should be improved, I'm opened to ideas as to how.
I like the idea of "Underlined inputs". The screenshot show a very minimalistic theme that can be customizable just changing a few colors.
I like the underlined inputs as well. For me they work well to separate buttons from inputs, which right now look almost identical. I believe when this issue was first posted underlined inputs weren't a common style to use, but now they are quite common.