Bugzilla – Full Text Bug Listing
| Summary: | need a "branding" page which is the default page when there is no user logged in | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> | ||||
| Component: | Client | Assignee: | Anton McConville <antonm> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | antonm, ian.skerrett, malgorzata.tomczyk, simon_kaegi, susan, Szymon.Brandys, tomasz.zarna | ||||
| Version: | 0.4 | ||||||
| Target Milestone: | 0.5 M2 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 372512 | ||||||
| Bug Blocks: | 378758 | ||||||
| Attachments: |
|
||||||
|
Description
Susan McCourt
We could also reload the page which would prompt for login, or go to index.html. Ken and I discussed this a bit. We really need a dedicated "branding" page that shows up when you hit an orion server and haven't logged in. It tells you how cool Orion is, shows you the logo and fun branding, etc. This is not "getting started" but rather "welcome, aren't we cool, sign in or request an account" Once you are logged in, then what we've been calling the "landing" page is shown. That is the home page for an authenticated user, and Ken is working on that in bug 345622. So...this bug is really about designing the "branding" page and then making sure that our authentication code always sends you to this page when there is no user logged in. Ken would like to take a crack at this page. cc'ing Szymon/Gosia as I'm sure we'll need your help for tying it all in. As a side note, maybe this branding page should try to cross the visual gap between the foundation landing pages (http://eclipse.org/orion/) and our standard look. Linda might be able to help with this. Note that the current login page is using the old styling. It is generating its own simplified header. I think for 0.4M2 it would be good to at least change the branding on this page to match a little better with the new header. (It doesn't have to be the same, but we should get rid of the black stripe.) At the bottom you mean? The grey stripe? Created attachment 209930 [details]
screenshot
the header is using the old logo and dark toolbar thingy.
We talked about a "branding" (not landing) page that would serve this purpose (the redirect page for a non-logged in user).
Even if it's just the old logo without the toolbar, that would be better.
Hooking it up to be the default page, making it nice, etc. can happen post-M2 but it would be nice to make it match a little better.
Ok, I wasn't thinking of the 'login' page, just the landing page. I see that now. I was thinking a little what could be presented on the welcome/branding page. Looking at other examples it seems that useful info is: - the logo - the login form - a create user/account form or a link to it - brief and catchy description of the tool, for instance: "Orion is amazing tool that can help you change the world. It has the best editor in the world and support for Git best ever etc." - the same links that we have in the footer i.e. FAQ, Report a bug, Privacy Policy etc. - info area. John asked to add a link for service related messages like maintenance hours etc. We could also show a link to N&N, but IMO it would be cool to show descriptions of newly added features in a random way. So if there are 4 new features, you will see just one at the time, but after refresh you will see another. And of course this advert area could be used for announcing anything e.g. talks on EclipseCon, new books about Orion :) (In reply to comment #0) > When I signed out (from > the repositories page), the only visual indicator that I'd signed out was the > user menu changing from userid to "Security." I stayed on the page, could > still see my repos, etc. Would be good to set the page to the login page? One problem we have here is that in 0.3 we assumed that we don't log in to Orion, but to Orion services. When we have one service than we can safely assume that logging out from it should redirect us to the branding page. But when we have more than one we would have to know somehow that this page was loaded using service we just logged out from, so we should redirect. We'll have the same problem with embedding the log-in form on the branding page. Not only there may be more that one authentication service, but also not necessary authentication will be performed via form. It may as well be basic auth, openid or anything custom. But we can add an "sign in" link like we have on the log-in popup. (In reply to comment #3) > Note that the current login page is using the old styling. It is generating > its own simplified header. I opened Bug 369490 for this. (In reply to comment #8) Right, if we sign out from one service it does not mean we are signed out from all and we should be redirected somewhere. I can imagine the following case: 1) have fs service 1 with auth service added 2) have fs service 2 with no auth service 3) log in to both 4) sign out using auth for service 1 So looking at our auth services we are not logged to any fs services, but we are logged in to fs service 2 still. I think that the best thing we can do now is to reload the page. Then if we are not logged in to any services required by the page, we'll be just asked to log in. Now the branding page. If Orion makes a call to a fs service and the fs service returns 401, we are redirected to the auth page of the fs service (using redirectURL returned with 401. This auth page could look completely different from the calling Orion client. Maybe Orion could pass some extra details about what it wants to display on the service auth page. For instance we could add extra details to redirectURL which could be then used to decorate the auth page. So auth page of a fs service could look different depending on what calls it. We would need to specify the format, how and what can be passed with redirectURL and of course we should be prepared that not all auth services would support this extra "injected" data or would support decorating data just from trusted Orion clients. *** Bug 371239 has been marked as a duplicate of this bug. *** are we going to do anything here for 0.4? The main short term issue is a user-less page to redirect to after logout. changing milestone since we didn't do this for M2... Still trying to address this. Working with Gosia to find a way to determine how one is not connected to any authentication services (not logged in). Deferring *** Bug 377001 has been marked as a duplicate of this bug. *** moving to Anton. I think we should first have a discussion with Simon, Susan, Anton to make sure we are all on the same page with workflow. Simon was suggesting that perhaps login would go away completely and the user could be dropped into a "disconnected" usage mode where they could immediately start working on a project. Maybe I'm too tied to the way most sites work now, but I think I'd like to first land on a "here is Orion, do you wanna do some work?" page. Even if I didn't want to login, I'd like a chance to decide if I'm ready to take to plunge into trying it. So maybe this page is: - welcome...you can... - test drive - login - create an account I'm not sure if this is the right bug, but Susan mentioned we should be able to test drive before login. I talked to Simon couple days ago about what should be possible for non-logged users. I think that it would be cool, if such users could create a file, edit it and save. This file would have its generated URI which could be shared between users. So Orion could be used as a scratchpad. (In reply to comment #17) > I'm not sure if this is the right bug, but Susan mentioned we should be able to > test drive before login. > > I talked to Simon couple days ago about what should be possible for non-logged > users. I think that it would be cool, if such users could create a file, edit > it and save. This file would have its generated URI which could be shared > between users. So Orion could be used as a scratchpad. FWIW, I wouldn't worry about implementing a non-logged user scenario. Just focus on making it dead simply to login. Wow, what a difference! Nice work, it's so welcoming! I think this addressed for now. If there is no "logging in" then you get redirected to the navigator. Much of the first time user help is available right there. |