1101009 - Design MVP of build.webmaker.org

Status: RESOLVED FIXED

(Webmaker Graveyard :: webmaker.org, defect)

Comment 1

[Ricardo Vazquez [:ricardo]]

Hey Bobby, Cassie directed me to you to get some details about this bug. Is there an Etherpad or a deliverable that I could take a look at?

Comment 2

[Bobby Richter [:secretrobotron]]

We're starting to work on the details! Will get planning done this week: https://etherpad.mozilla.org/buildwmo

Comment 3

[Matt Thompson (@OpenMatt :OpenMatt)]

* Andrew created a whiteboard here -- included here: https://wiki.mozilla.org/Webmaker/Build

Comment 4

[Matt Thompson (@OpenMatt :OpenMatt)]

* Ricardo and Matt reviewed the basic whiteboard together after our kick-off call

Comment 5

[Matt Thompson (@OpenMatt :OpenMatt)]

* Here's a wireframe
http://mzl.la/build_wireframe

* Andrew: you suggested a couple buttons in the main panel as well, I think -- am I missing something?

Comment 6

[Ricardo Vazquez [:ricardo]]

Attachment: https://redpen.io/p/uzc8a66faaf0d225a7

Comment 7

[Ricardo Vazquez [:ricardo]]

Attachment: https://redpen.io/cs942ed750d65e57df

Comment 8

[Andrew Sliwinski:thisandagain]

This looks really nice, but the scope of this seems a little unclear (and quite large). As I'm not the primary stakeholder here, so I'll just put a few pieces of content that I had hoped we could include (as per the sketch) for discussion:

- What? 2015+ Product planning
- Who? Personas / user stories
- Why? Field research and user testing reports
- How? Tools and process documentation

We had also discussed having "When", "Now", and "Add Project" sections that could help folks understand where we were focused on a sprint-by-sprint basis as well as submit new projects to ensure that the process could shift as we learn along the way and give TPS a much needed input channel.

Comment 9

[Ricardo Vazquez [:ricardo]]

Hey Andrew, I think that the pieces of content you are looking for are all there, but they've been categorized in a bit more depth (might be talking out of context, I haven't worked on the IA). In regards to the "When", "Now", and "Add Project" sections, they are being displayed in the Heartbeats section of the website design. I added "Current Heartbeat", "Around the corner", "On the horizon", "Add a project", as well as "Initiatives". This is the screen: https://redpen.io/su08b1a9a81eda876d

I'm creating the UI based on the IA that Cassie and David have worked on. Let's loop them in to make sure all our bases are covered and we're covering everything and/or haven't bit off more than we can chew.

Comment 10

[Andrew Sliwinski:thisandagain]

Thanks! Sounds great, just curious where the IA is living as there is a disconnect between what Matt has represented here (https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/qv96_6s7.png) vs. here (https://redpen.io/cs942ed750d65e57df).

Comment 11

[Ricardo Vazquez [:ricardo]]

Oh that I can answer! The IA ticket is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1101764. In the bug you will find a link to a Google Doc.

Comment 12

[David Ascher (:davida)]

There are two competing views on this:

1) a content site with all of the assets, links etc. that represent what we're building in 2015 and how.
2) a dynamic process-helping site which is about communicating near term plans, up to date status on things-in-progress, and ways to inject new needs into the plan.

I believe Cassie and Ricardo are focusing on 1), but I think Andrew, Matt and David are more worried about 2).  They're not incompatible, but I don't think we can or should do both as an MVP.

W.R.T. 2), I know of two things: Wex's google form: http://goo.gl/forms/Wu2dOyUNoE and the 'binder' thing I worked on yesterday, playing around with jekyll + prose last night to explore how easily we can have a site that is templatized and has custom CSS but still has the easy editability of a wiki.  What I have is currently at http://mozillafoundation.github.io/binder/

It really just tries to support a small # of use cases:
 - create a new initiative
 - organize initiatives in sprints
 - surface currently planned sprints
 - make page editing in markdown possible through the web 

(editing requires membership in a specific github repo, ricardo let me know what your github ID is and I can add you).

I suspect some integration of this kind of tooling, ricardo's styling, some negotiated IA for the content itself, and some version of Simon's google entry form  and we're done w/ MVP, we just have a very small # of days to do it.  We can lean on sprinter or codetree or whatnot off of those initiatives.

Ricardo: If curious the templates for the 'binder' are at https://github.com/MozillaFoundation/binder

-----

Cassie and I met and chatted about audiences and structure.  What we ended up with is in the gdoc under the section "David's thinking out loud".

Comment 13

[Cassie McDaniel [:cassiemc]]

Thanks for the updates, all. I'm okay with moving forward with "2) dynamic process-helping site". But would like to note that this bug was intended to build the bones into which we plug other dynamic tools or links (such as intake form), we had not intended to build those tools themselves as part of this MVP. I think it's really important we start with the scaffolding to avoid further link sprawl.

Also note, David surfaced another important requirement here, which is to ensure build.webmaker.org has some modicum of editability. We should do some exploration here. David's instance is an awesome start or perhaps does already meet the MVP requirement.

Lastly, a PROPOSAL TO PUNT: OpenMatt suggested we use Portland to put our brains together and get closer alignment here. I agree. In the meantime, this is great progress Ricardo and gives us basis for gaining consensus.

I'll keep moving the IA along in bug 1101764 and I'll flag people for review there.

Comment 14

[David Ascher (:davida)]

Moving the design conversation to https://github.com/MozillaFoundation/plan/issues/150.  I think we can close this bug.