cashmusic / ux Goto Github PK

The new proposed login page. It's a login page. We're trying to encourage ease of login, but with the ability to use Mozilla Persona, potentially other services, etc.

Comments below, Jesse, from Suz, sent to you awhile ago.

My main issue with the admin is the problem with loading hundreds of individual images when looking at our list of imported projects. Nate Bedortha btw said he thought he had a solution for this.

Now from Suz:

First, as mentioned, the platform is easy to use. I like it.

I have some preliminary questions after entering my first project. Without seeing what the completed pages look like, this is the extent of it for now. Once I see how the assets are presented on a page, I may have additional questions.

Regarding the Assets page --

1. will there be a search feature? It will be helpful to be able to quickly access older projects for editing

2. is it possible to include the artist name on the projects that appear on this page? If I don't know the album name it'll be helpful to be able to view by artist, or at least see the artist name listed somewhere

Regarding the "Miscellaneous" category within each album --

1. after I entered a photo, my only choice was to go back to the main Assets page. It would be nice to be able to stay within the "Miscellaneous" category for entering various assets, without having to jump out of it and back into the album, then back in to the category.

2. should I upload the project's label logo to this category? I'm not sure how the various assets are presented on a completed page so I wasn't sure where to enter the label logo but I'm guessing this is the place

Regarding the music upload section

1. possible to upload all music files at once? If not that's fine. . .would go more quickly but is not a big deal

Other questions --

1. Is there a place where I can enter links that are of relevance to a particular album? Such as social media site URLS?

A major focus of this round of UX enhancement will lie with moving everything currently in the "Elements" section onto the main page, creating a top-down experience that puts most common tasks right at hand. (Some discussion about this in issue #1)

The main features of this page:

• An activity stream instead of a dashboard. This will be based on events in the system that can trigger activity milestones, and the user can filter what types of milestones they see. Shown here are the main types, which come from all over the platform:
  • Simple milestone (link and description)
  • Analytics (visualization, link to expand)
  • News (system administer chooses news feed)
  • Urgent system notification
• A simple element list, sorted by most activity+date added. Friendlier copy about elements and link into the FAQ. The "add new element" but ton that will open an element selection overlay and individual element wizard a la current "simple mode."
• Simpler approach to talking about page publishing. Quick access to embed codes (also avaiable on element pages) and element embed template management.

Here are all the non-form page elements and chrome for the proposed UX revisions in the admin. Brand aside, the focal points are:

• All navigation up top, including settings and help. No more confusion about where to click primary app navigation/interface.
• Better use of icons throughout major navigation points.
• Consistent typography (Roboto Condensed Bold) for interface-level links. (The exception being for in-copy links.
• Narrower main column layout. Too much horizontal space was an issue, leading to awkwardly long inputs and hard-to-read copy. This allows us more legible full-page copy while keeping the ability to keep using 1/2/3 columns for form layouts. (And making single column forms not stupid.)
• Better list styles.
• Multiple sizes/weights of text, normalizing around 14px and going slightly up/down where needed.
• Link color tied to sections as before, but in a more subtle way.
• The merit badge icons as subtle touchstones for each section, will tie in to color coordination.
• Consistent location (under page title) for sub-page, in-page, and section-home links.

Hello! First post here. My full-time job is in UX, but I spend my free time playing in a band and hosting a radio program for a community-supported station.

I've played a bit with the self-hosted and hosted versions, and I have a question to ask: After logging in, what is that CASH would like a user to do? I realize there are lots of things users could do, but I can imagine for someone who's not familiar with the service, they are probably thinking, "I'd like to accomplish X."

I really like the yellow callout panel because it follows the established UX principle of providing signposts & cues. I know what I can do with that. (Of course, if I don't have any elements, then this callout is not helpful.)

However, it's the only callout. And it sets up a problem: If this is my first visit, what do I do if I have no assets or elements?

Perhaps we can brainstorm another 3-4 concrete tasks and develop additional callouts that can lead users through a set workflow?

Here are a couple things I came up with:

• Set up tour dates.
• Add new press clippings.
• Sell an item.
• Add a record to my discography.

It might be a good idea to poll some of the public beta testers about what they wanted to do first?

I've been doing a lot of thinking, largely inspired by @theoreticalgirl and the need to radically simplify the admin interface for new users. Right now we're basically throwing people into something as complex as Quickbooks without much in the way of introduction, documentation, etc.

I honestly think the admin interface is generally as simple as it can be for something that is a pretty complex tool. We've got lots of room for improvement, but the concepts are solid. That said, not everyone wants all the complexity.

Because people have different needs and learn at different paces, I think we should take a cue from modern webapps and offer a single-task driven simple interface for new people. Rather than just a tutorial, people should be able to use the platform in this simple mode until they need more — at which time we graduate them to the full interface and their experience will reinforce those concepts so we can rapidly get them up to speed.

Here's a huge mockup of the new workflow: