There is only one login mechanism. Nothing is hard-coded. The only meaningful difference is what the login widget looks like and where it redirects after login.
It's entirely a question of UX. * Admins who want to hack on the site know to use [root]/login which will direct them to the Aiki panel. If their session expires on the admin panel they will be redirected back to [root]/login by default, from where they can log back into the admin panel. * Admins (or anyone else) who want to hack on fonts know to sign in from the home page. If their session expires they will be directed back to the sign-in page. (Keep in mind that Admins who sign in anywhere are signed in site-wide, admin panel and website.) Now, all of this can be changed. The default /login page is just another widget. It can be easily restyled to say OFLB instead of Aiki. It can move to a different URL. Admins can be directed to /admin and everyone else to the home page. Or Admins could get an "aiki" link on the OFLB header (only visible to signed-in admins) that links to /admin. In the final analysis, however, having two login points is of great convenience to the site designer. -- You received this bug notification because you are a member of Open Font Library Developers, which is subscribed to Open Font Library. https://bugs.launchpad.net/bugs/728872 Title: users need a separate sign-in page from admins Status in Open Font Library: In Progress Bug description: The current "Log in" in the header links to [root]/login, which is the sign-in page for admins. The link could instead read "Sign in" and must point to [root]/users/sign_in or [root]/users/login A widget then needs to be available on at that url to handle sign-in _______________________________________________ Mailing list: https://launchpad.net/~aikiframework.admins Post to : [email protected] Unsubscribe : https://launchpad.net/~aikiframework.admins More help : https://help.launchpad.net/ListHelp
