• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

Real World: The users ask "How do I login?" I tell them to look at the top of the left menu bar. "Oh!"

Its just as easy to have the login form there as the link to a page with a login form.

Access violations still take the user to a login screen. A popup would be nicer.

See screennshot

Although your approach to make the login facility more visible serves it not being overseen but is contraproductive in terms of GUI simplicity aka information overflow. What if I already know how to login and I don't want to see the form again and again? Banner blindness follows.

  • What if the site is resticted and you must login to visit anything but the home page?
    Hence you don't see it again and again.
  • The 'old' arrangment has the link go away and the 'personal' appear. Same here. You don't see it on every page. -- AJA

In general, it is totally acceptable to be just one click away from the information you need. But no more! Therefore hiding the login dialog behind a login link is absolutely fine and toleratable. Especially if all things follow the one-click-distance principle: performing a "if you want to do this then click here".

  • This approach seems to elminate 'how do I log in' questions form users who are used to seeing the log-in form "up front" at othersites. Why they don't notice the "Login or Register" as links rather than exhortations I can't tell you. -- AJA

Note further, that extra gear that you put around the main area becomes part of every page and distracts the visitor from the real content. If there's any way to hide stuff without blurring functionality beyond recognition.

I like an approach where the wikiness of a site is not obvious, but only when you demand it. That's why topic actions as well as the login facility should be there but not so multipresent.

IMO, popups are a GUI-no-no, especially when they pile up between you and the application. "No, please do it ... don't ask me for the same question again ... must I click on ok, cancel or ignore." GUIs feel better if they are made rock-solid without the need of modal dialogs.


If you're willing to use javascript you can have your cake and eat it too: the logon text is a link, but when you click it instead of taking you to a new page it expands the logon form. Drawback: the form would be sent with every page, adding to overall page bloat.

If you're designing for an Intranet/extranet it makes sense to put the login prominent. For public websites I find it too distracting to put the login fields on each page.

The js (toggle) idea is neat but as said adds to the page - of not logged in viewers only.

Part of the neatness of the login on the page is lost because the page should be anyway after logging in (perhaps buttons are enabled then or made visible).

I don't see a bug in here (perhaps a cookbook entry) so I suggest to move discussions to Codev.


Undeferred, post Dakar CC

Summary Usability - users should not have to go to another screen to login
ReportedBy AJA
SVN Range

AppliesTo Engine

Priority Enhancement
CurrentState New

TargetRelease major
Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng ISW11.png r0 manage 105.3 K 2005-10-20 - 10:50 AntonAylward Illustration of working code to put login for in left menu bar
Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r7 - 2006-02-13 - CrawfordCurrie
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback