Closed (fixed)
Project:
Pushtape Music
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
9 Jan 2012 at 04:40 UTC
Updated:
16 Aug 2014 at 21:20 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
zirafa commentedFirst pass at a sitemap.
Home
- Toolbar
-- Archive
-- Search
-- New...(track, photo, blog)
-- Admin
--- Content overview
--- Account
--- Statistics
--- Design
--- Settings
- Blog
-- by date
-- by tag
- Photos
-- Gallery overview
--- Single gallery
---- Photo
- About
- Contact
- All Releases
-- Individual Album
-- Individual Track
Comment #2
zirafa commented2nd Draft, clearer split between Admin side. Still not sure about a lot of the terminology...
Comment #3
zirafa commentedSimplifying the sitemap and removing a bunch of pages that don't make any sense at the moment (Import/Export, Widgets, etc)
Comment #4
zirafa commentedHere are two sorta generic block diagrams for interior page layouts (excluding admin pages). NEW ... FORM is a quickpost form for creating new content (think Facebook or Tumblr).
[1] INTERIOR PAGE LAYOUT, ADMIN LINKS ANCHORED AT THE TOP

[1a] INTERIOR PAGE LAYOUT, ADMIN LINKS MORE INTERTWINED WITH CONTENT

Comment #5
zirafa commented[1c] ANOTHER VARIATION. ALL NAV LOCATED AT THE TOP OF THE PAGE.

Comment #6
zirafa commentedGetting back on task here to the sitemap. Here is a concrete default sitemap, showing navigation structure as well as tying individual pages to template pages that need to be designed. It is pretty final, although I might make some minor adjustments. The next step is to design wireframes for each template listed. Strategies for creating the wireframes: evaluate personas, do pre-wireframe exercises on paper, decide key content blocks and rank their importance for each template.
Comment #7
zirafa commentedI made up 3 personas (Kip, Cindy, and Liam), I really encourage other people to create more personas following this format. It helps prioritize functionality on the site which helps the design process.
PERSONA 1
Name: Kip Wilkinson
Age: 20
Lives in: Austin, TX
Occupation: Bassist. Works part-time at a grocery store, and also takes 5 credits at a local college. Plays in a band called the "Kingstone Flappers" made up of 3 members: Kip, Luke (drums), and Tom (guitar & vocals).
What type of activities does he do online:
What types of activities compete for his time?
What activity does he perform on your site?
How did he hear about your business?
General notes:
Persona 2
Name: Cindy Beckman
Age: 33
Lives in: San Francisco, CA
Occupation: Works at a design firm. Does web and video editing gigs on the side. Plays drums, guitar, synthesizer, performs as a solo artist at local clubs under her own name.
What type of activities does she do online:
What types of activities compete for her time?
What activity does she perform on your site?
How did she hear about your business?
General notes:
PERSONA 3
Name: Liam Fullerton
Age: 45
Lives in: Chicago, CA
Occupation: Works at a record shop and a music venue. Manages a few bands and plays guitar in an experimental electronic group called "ThunderSplat" - they don't perform out very often but spend a lot of time in the recording studio.
What type of activities does he do online:
What types of activities compete for his time?
What activity does he perform on your site?
How did he hear about your business?
General notes:
Comment #8
zirafa commentedPrioritizing all the Personas I have (a couple were e-mailed to me) and ranking importance of each activity, I got this list.
Statistics[not in 1.0]E-Commerce[not in 1.0]Comment #9
discipolo commentedjust for verification:
Comment #10
zirafa commented@discipolo
Correct - in this scenario each persona is the site owner and single user of a Pushtape instance. Things would change if visitors were expected to login (something to explore in the future, for sure).
Yes. Just adding more background info about how this person came to use the software.
Comment #11
zirafa commentedI may have misinterpreted what you meant by visitors - it could be useful to do this again for anonymous visitors of a site, i.e. fans visiting a site too. But for now just focusing on the main user and what they are trying to do with their site.
Comment #12
drupaljohngo commentedIs your strategy changing due to some of the features in Html5? Canvas for instance?
Comment #13
zirafa commentedI'm not sure I understand the question, how would HTML 5 / Canvas change the strategy?
Comment #14
zirafa commentedHere are the wireframes [PDF] done in pencil. It was too big to attach to this thread. Also sorry for the messiness as I used pencil & eraser. There are probably some wireframes missing but 80% of things are shown here and should get things started. It would probably be helpful to create HTML wireframes from these that demonstrate responsive behavior and to help iterate through styles. I could use some help with creating HTML wireframes.
Notes:
1) The simplified admin dashboard and interface here is for USER 2 (the main user). USER 1 login is for experts and drupal developers ONLY. The admin interface is the #1 most important part of this whole project. Distro audiences should expect and receive a full non-developer product experience, as if they were logging into a regular site. (Except it is THEIR site.)
2) Toolbar + messages are "sticky" at the top of each page. When you scroll the page, they stay at the top. The authoring workflow all stems from the upper left corner Tumblr/Facebook style area. The "quick post" form is a fast way to create short news posts. The idea behind this is the author should ALWAYS be one click away from creating new content.
3) The Tracklist view needs to support progressive enhancement using SoundManager, HTML 5 etc for playback. But it should still work fine as a discography list. I tried to make the tracklist + artwork look like one unit, but this could use some more thinking.
4) The music dashboard is still a work in progress.
5) Theming / personalization is a big question mark right now. Part of me wants to just restrict this to developers for now, letting the design rely more on uploaded images and some CSS settings for colors and fonts. The default theme should be stable and functional above all else. Adding new themes later is easy, getting a good default theme out-of-the-box is hard.
Please keep in mind the context of these wireframes - the goal is to satisfy the needs of the Personas as listed above.
This is not meant for technical review, so no tech discussion, please! Keep it about the design & user experience.
Comment #15
zirafa commentedMoving forward with PDF Comps...
See: http://drupal.org/node/1398280#comment-6119206
Comment #16
lsolesen commented