search

backdrop / backdrop-issues

Issue tracker for Backdrop core.
145 stars 40 forks source link

[META] [UX] Backdrop First Run UX #1663

Open wesruv opened 8 years ago

wesruv commented 8 years ago

We're talking about a lot of high level changes to the site builder experience, want to make sure we think of these as a whole and how they work together.

These could totally change, in case anyone wants to try something different.

Logged in

image

Logged in, Get started pane open

image

Logged out

image

Logged Out, Login box open

image

wesruv commented 8 years ago

Running into an issue while working on this stuff.

The block-system-header is a total headache. Being able to have a menu in the same block as the logo, slogan and site name, and having that menu default to the account menu is a nightmare.

From a design perspective, not many people put the account menu next to their logo. That'd be reserved for the main menu.

Even if we defaulted to the main menu, it feels really inconsistent to have a block that kind of has a block inside of it, so for the current default config I'm trying to move the account menu to the top right corner where it makes the most sense to me. This is making the contextual menu impossible to hit, and could cause lots of other issues.

I'd much rather have the default config have three blocks in the header:

Each block has a single function, have it's own space (preventing contextual menu hover issues), and it'd feel more consistent.

Can we update the default install profile to be something more like this and deprecate the menu in block-system-header in v 2?

klonos commented 8 years ago

It always seemed kinda funny to me why we have a single, magic "Header" block that includes a bunch of things that could/should be individual blocks themselves. It makes quite a few assumptions that lead to a UX with very limited flexibility when it comes to where people can place/move things.

Having said that, @wesruv you might be interested in #1704

wesruv commented 8 years ago

I suuuper want that too!

klonos commented 8 years ago

Then please do voice that on that issue :wink:

Bojhan commented 8 years ago

One thing I would recommend is not to intermix the "tutorial" part in the actual demo theme. Learning from D6 mistakes here.

If its in the demo theme we know that people 1) get frustrated they lose the steps, 2) are unsure what is part of the system and just part of this demo theme, 3) don't find the actual way to functionality and are only able to do it through links in the demo.

Ideally you have a tour, or similar concept to expose steps as to where to go.

wesruv commented 8 years ago

Thanks for the insight @Bojhan, I think we were on track... I definitely did not have those specific points in mind, and those are some very good points.

The plan is to make it a stand alone module, that could be easily disabled/extended/etc. Even talk about making it a to-do list module and this Getting started checklist could be some default config that's part of an install profile (if not the default, we've discussed a tutorial/walkthrough profile).

Point 3 is especially interesting... I think we'll need to do some thinking/testing to make sure we're "teaching how to fish", probably won't get that right on the first try.

ghost commented 4 years ago

Anything still actionable and relevent here, or should we close?

klonos commented 3 years ago

There are still some pretty good ideas here (will need child-issues created for each one of them, as time permits and people have the energy/time to work on them).