WEB SITE LOGINIs there a reason a simple link or weblink, to a page that contained the weblogin bits would not work? That’s a simple implementation decision, or am I not understanding the requirement?
My requirements include: “Until the user follows a login link, he should not
see a login box, a password box, a registration link, or a lost password link.
This decreases irrelevant clutter.”
WEB SITE LOGINIs there a reason a simple link or weblink, to a page that contained the weblogin bits would not work? That’s a simple implementation decision, or am I not understanding the requirement?
My requirements include: “Until the user follows a login link, he should not
see a login box, a password box, a registration link, or a lost password link.
This decreases irrelevant clutter.”
Further help me understand the previous/next links bits if you could. How many websites do you see that actually implement this, and why is this a requirement for evaluation? It would be trivial to author a snippet to parse through the menu indexes of the pages in your site and create those links. How do next/previous links work in sites with deep hierarchy? How would they work on a site like apple.com or adobe.com or any non-blog site for that matter?
[2] Management interface usability would be rated "excellent" for both CMSes if they provided protection against accidental erasure of the contents of a web page.
I don’t get this part at all. Deleting a document in the MODx manager is a two-step procedure: You can still un-delete a page if you want to, and there’s warnings popping up if you want to delete stuff. If people then still "accidentally" erase content... guess it’s more of a user-error than a flaw with the application.
But the real problem here isn’t so much deleting a page, which is rarely fatal in MODx, but overwriting its contents, which is always fatal. If you absent-mindedly hit ^A to select the entire page while editing it, then type a couple of words and then save, you are SOL.
Quote from: rthrash at Jan 23, 2008, 07:06 AM
WEB SITE LOGINIs there a reason a simple link or weblink, to a page that contained the weblogin bits would not work? That’s a simple implementation decision, or am I not understanding the requirement?
My requirements include: “Until the user follows a login link, he should not
see a login box, a password box, a registration link, or a lost password link.
This decreases irrelevant clutter.”
A single link entitled ’Sign in’, ’Log in’, etc., is all you need. You can see this in use at http://www.google.com/, http://en.wikipedia.org/, and http://rahul.rahul.net/, among others. However, after logging in, the user should be able to easily return to the page from where he came, and various web sites succeed in facilitating this to various degrees. At http://en.wikipedia.org/, you just follow another link to return to the page. At http://rahul.rahul.net/, you need to use your back button a couple of times (not so good). At http://www.google.com/, most of the time, you end up where you wanted to be after you log in, but in some cases, you do not, depending on what you were trying to do. So implementations vary in their quality. Ideally, after you log in, you should find yourself back on the page from where you followed the login link.
You can see it NOT in use at http://www.drupal.org/, http://scottydelicious.com/, and some of the MODx web sites, all of which repeatedly present a login box, a password box, a lost password link, and a registration link, to every user, on every screen, whether or not the user has any intention of ever logging in or registering.
More later re your second question.
Rahul
WEB SITE LOGIN
My requirements include: “Until the user follows a login link, he should not
see a login box, a password box, a registration link, or a lost password link.
This decreases irrelevant clutter.”