Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UX] Redirect to the Dashboard after install #4673

Closed
jenlampton opened this issue Oct 2, 2020 · 25 comments
Closed

[UX] Redirect to the Dashboard after install #4673

jenlampton opened this issue Oct 2, 2020 · 25 comments

Comments

@jenlampton
Copy link
Member

When we install a new Backdrop site, we redirect people to the front page immediately after logging them in. But once your backdrop site is up and running, we redirect people to the dashboard immediately after logging them in.

I'd like to recommend that we redirect people to the dashboard after installation.

Follow-up to #4162

@stpaultim
Copy link
Member

stpaultim commented Oct 2, 2020

This issue is at least in part inspired by watching a new contributor (during Open Source Day) navigate around the site trying to find where to update the site name and logo. I expected them to find the dashboard and all the helpful tips that are on the dashboard, but this user never found it until we suggested they click on the dashboard link.

I think it would be helpful for a new user to know that this dashboard page exists and that it might be a good place to go for basic help.

@klonos
Copy link
Member

klonos commented Oct 2, 2020

I won't object to this change if that's what most people agree is the best UX, but wanted to express my opinion.

Manually logging in vs. being automatically logged in once the installer finishes are two different "user journeys". Once the site installation has finished, people are likely to visit the site's home page, to click on the "log in" link. This means that they get to see what a freshly-installed Backdrop site looks like, so it makes sense to redirect them to the Dashboard after they log in. When the installer finishes though, the person performing the installation has no idea what the front page and the frontend theme looks like, so IMO it is a good thing that we are not redirecting them to the Dashboard.

Now, I don't deny the UX issue here, since people seem to miss noticing that there is an admin menu bar at the top; perhaps they do notice it, but it just seems overwhelming because there are so many options in there. I think that there's a way to solve this, while still allowing people that install Backdrop to get a peek at what the site they just installed will look like for their site visitors. So how about instead of redirecting them to the Dashboard, we add an "info" message right bellow the "Thank you for installing Backdrop" success message? Something with a link to the Dashboard, like this:

Tip: You can use the admin menu at the top of the page, to navigate around the administrative interface. If you are new to Backdrop, then the Dashboard may be a good place to start.

@stpaultim
Copy link
Member

I will look at your PR. I do view providing contextual help to find the dashboard might be an alternative to this solution.

I agree that there is value in landing on the front page after install. But, I would also argue that it's much easier to get to the front page from the dashboard than it is the reverse. I'm not fully decided on which option is best. I just think it's important that we help new site owners find the dashboard quickly.

@jenlampton
Copy link
Member Author

When the installer finishes though, the person performing the installation has no idea what the front page and the frontend theme looks like, so IMO it is a good thing that we are not redirecting them to the Dashboard.

I think it's a bigger problem that people don't know what to do after they complete the installer. The Dashboard has a lot of helpful links to other things they can do, the home page has nothing. :(

@stpaultim
Copy link
Member

@klonos - Is there a META issue for issues related to this? (I'm not sure what they would be)

@klonos
Copy link
Member

klonos commented Oct 5, 2020

I will look at your PR.

There's a silly mistake in it which brings up fatal php errors (I just whipped it up via the GitHub web UI 😅 ) ...I've fixed it on my local but I'm having issues pushing to that branch for some reason.

Is there a META issue for issues related to this?

Not that I know of 🤷

The Dashboard has a lot of helpful links to other things they can do, the home page has nothing. :(

Yup, that's why I'm proposing this:

image

@klonos
Copy link
Member

klonos commented Oct 5, 2020

...PR (manually) updated.

This will need testing on one's local.

@stpaultim
Copy link
Member

stpaultim commented Oct 8, 2020

This works as expected, but not as requested in the original post. ;-)

i believe that this PR is a clear improvement over the status quo - pending some text changes. I do not have a strong preference between this option or the suggested solution to redirect to the Dashboard after installation. I see pros and cons to both.

Regarding text changes. I do not think that the message about the admin menu is very helpful and adds clutter. I believe that the admin menu is pretty easy to see and find. Do we have any evidence that new users are having difficulties finding or understanding the admin menu?

I think a simpler message that is focused on finding the Dashboard would be more helpful.

"Tip: New users should visit the Dashboard for ideas on how to get started with your new Backdrop CMS site."

@stpaultim
Copy link
Member

stpaultim commented Sep 12, 2021

This issue has not had any action in almost a year. I added it to the agenda for the next UX meeting to see if we can break the logjam and decide on a path forward (or to see if there is interest in this issue)?
https://docs.google.com/document/d/1C42vvx0U61Hmj1HKsbOULtEOV0XWI4Y0KrOKvej1Zi8/edit#

@jenlampton
Copy link
Member Author

jenlampton commented Sep 13, 2021

I just happened to talk to @quicksketch about this yesterday, and he said that he likes that you get taken to "your website" after installation. He said that WordPress does the same thing. (needs verification)

I can see the benefit of showing someone a fully functional website (before they do any configuration), even if it does leave people with the "What next?" reaction. I would expect the natural "next" action would be to explore, starting in the top left, seeing the admin bar, reading "Dashboard" and navigating there to find all the goodies.

I wonder if this should get some user-testing?

@stpaultim
Copy link
Member

stpaultim commented Sep 13, 2021

I wonder if this should get some user-testing?

I'm in favor of user testing it. However, if you remember we had a single informal user test that at least partially lead to this issue being opened: #4673 (comment)

Of course, one test is not enough.

@klonos
Copy link
Member

klonos commented Sep 13, 2021

I can see the benefit of showing someone a fully functional website (before they do any configuration)...

Same 👍🏼

I would expect the natural "next" action would be to explore, starting in the top left, seeing the admin bar, reading "Dashboard" and navigating there to find all the goodies.

Only (more) user studies would shed light on that (whether the "Dashboard" link in the admin bar, or the admin bar itself are easily discoverable).

We already provide an obvious/prominent way for people to get from the Dashboard to "the website" (via the "View the home page" link in the "Welcome to Backdrop CMS" block). Perhaps we should similarly provide a more obvious/prominent way to go from "the website" to the Dashboard. That's what I was going for with this PR.

@albanycomputers
Copy link

I agree with @stpaultim that the status message could seem cluttered.

For me, the logical solution is to offer hints in the "Your first post" post... may as well make use of something that gives very little value to the install.

There are too many scenarios to mention... but the post "Your first post" will stay there until the user deletes it, whereas the status message will only appear once, so at least they have some pointers.

@klonos
Copy link
Member

klonos commented Oct 24, 2021

...you get taken to "your website" after installation. ...WordPress does the same thing. (needs verification)

Yup, it seems so. This is what I see when I try installing WordPress via softaculous (v5.8.1 at the time of writing this):

@albanycomputers
Copy link

A quick example...
image

@albanycomputers
Copy link

And something like should be really easy to implement, it's non-intrusive and may just offer that little bit of help a new user needs to feel as though they have made the right decision due to the helpful nature of the landing page after installing.

@klonos
Copy link
Member

klonos commented Oct 24, 2021

...the post "Your first post" will stay there until the user deletes it, whereas the status message will only appear once

I acknowledge that issue with info messages, but the in-content pointers also have an issue: we cannot add links to admin pages, as the user seeing that node may not be logged in. So in the screenshot above, the "Dashboard" link will work for the person that just finished installing the site, but it will not work for anyone else visiting the site and not being logged in. It will only work for site admins and content editors, whereas it will be a "broken" link in the front page of the site for anyone else.

Perhaps this content should go in a custom content block or something (that is has appropriate visibility conditions).

@klonos
Copy link
Member

klonos commented Oct 24, 2021

...shame that Dashboard-provided blocks cannot be added to any other layout. We could try to see what the "Welcome to BackdropCMS" block would look like if placed in the front page.

@klonos
Copy link
Member

klonos commented Oct 24, 2021

...so simple 😉

image

...advantages of the above solution:

  • Reuses existing code/content from the Dashboard module.
  • It is not implemented as a message, so it won't go away unless manually removed.
  • It is a block, so it can be shown only to people with appropriate permissions.
  • The various links provided also account for any required permissions in order to be shown or hidden.

This is what anonymous visitors will see:

image

We'll need to tweak a few things, like:

  • add some logic in the "view the home page" link, so that it is not shown if you are already in the home page
  • maybe hide the "More actions" heading if that's the only set of links available
  • perhaps hide the entire block altogether for anonymous visitors

...the point is that it mostly works out of the box 😉

@albanycomputers
Copy link

So in the screenshot above, the "Dashboard" link will work for the person that just finished installing the site, but it will not work for anyone else visiting the site and not being logged in. It will only work for site admins and content editors, whereas it will be a "broken" link in the front page of the site for anyone else.

Yeah, I thought of that... just hadn't gotten around to posting :-(

@albanycomputers
Copy link

albanycomputers commented Oct 24, 2021

The block with permissions is a lot better :)

And it makes the initial view of the site more appealing... well to me it does... lol

@stpaultim
Copy link
Member

Some of the content issues being discussed here are also being addressed in this other issue: Provide a new 'hidden-path' content type in core
#4903

@albanycomputers - This is a pretty long issue, but I think you might find it interesting.

@olafgrabienski
Copy link

I like the idea to put the Dashboard Welcome block also on the front page. Re things to tweak, I'd add a visible and clear option to remove the whole block.

@stpaultim
Copy link
Member

Since opening this issue, we've implemented a number of the ideas discussed and added a link to the dashboard. I'm inclined to close this issue as having been addressed in a different way.

@klonos
Copy link
Member

klonos commented Apr 12, 2023

For posterity, here's what you get after finishing the installation with #5624 (which got implemented in v1.23.1):
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants