Account page design

Thiblo is going to be a journal factory, allowing all journals to create and use their own look and feel, colors, etc. We don't even want or will to force them to include some header of thiblo, we just make things possible. However, the article pool and the user pool will be common for the journals. That means that we need an account page that is as neutral as possible.

The account page of the user is where he can change her settings, manage her journals, articles, everything. We plan to write it either in gwt or similar.

Graphically we plan to have an account page that has iGoogle like boxes in it for the individual tasks, with some minimal features provided. If a box is expanded, the whole page is dedicated to that certain task (like managing all my comments, or moderating incoming comments). It is sort of a zui-like interface.

The account page must be able to show in the title which journal the user has reached it from (and not only show just somethig like "thiblo account").

At first, we need to have 2 iGoogle boxes, one for "preferences" and one for "comments". Both of them show something reasonable (like the comments iGoogle box can show the first few words of the last few comments, etc.), and after expansion, the user can get the whole functionality.

The whole account page system should look and feel as much as native apps as possible, heavily relying on ajax. As for design: even basic xul look and feel is something that I can imagine. Some very basic blue line based design as is in our iGoogle test page is OK, but that is the maximum, no fancy colors or images (remember, a journal that uses that might be a cold color based design, might be a warm color based, whatever).


A user interface can be shown

  • in the browser, as a normal web page
  • in a popup window
  • on a layer

It would be awesome if we could experiment with all these, so if the account page user interface could be switched to operate this way or that way. I can't really decide what is the best right now. The 3rd option presumes a smaller account page which we can show by fading the current browser content and showing a layer on top of it, like what the current comment editor box does (without the fading).

At first though, the layered implementation is not only not important, but shouldn't be spent time on it. Just kept in mind, if some design or coding decision depends on it.