<div dir="ltr"><div><div>+1 to what both Cassie and Gavin have said here -- great discussion, and I'm definitely in agreement. I'm thinking that with increased documentation, Makerstrap can actually be even more useful than we expected, in two specific ways: <br>
<br></div>1) It can give us a vector for introducing external contributors to our open source design process and best practices for the first time, ie: <br>a) Using a 'style guide', and then <br>b) Asking for open source design review on it. <br>
This experience runs in a similar vein to Cassie's presentation about this topic last week. Would love to chat more about documenting how it could work for community contributors.<br><br></div><div>2) It can also show us what value people find in using a style guide to begin with, and what works best re: them providing useful feedback on it. <br>
For example, I found the gallery on the demo page hard to parse: <a href="http://mozilla.github.io/makerstrap/demo/#/">http://mozilla.github.io/makerstrap/demo/#/</a> This is something I could file a Github issue on, but this also is a situation where increased documentation on the demo page (and the repo itself) will ensure best practices here. ie, how to file a useful issue.<br>
<br></div><div>Thoughts? <br></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><a href="https://www.webmaker.org/" target="_blank">
</a>
<table style="font:14px/1.2 'Fira Sans','Open Sans',Helvetica,Arial,Sans-Serif!important">
<tbody><tr>
<td style="border-right:2px solid grey;padding:1em 1em 1em 0;text-align:center">
<a href="https://www.webmaker.org/" target="_blank">
<img src="http://stuff.webmaker.org/editorial-assets/unnamed.png" style="width:100px" alt="Mozilla Webmaker" height="100" width="100">
</a><br>
</td>
<td style="padding:1em 0 1em 1em"><b>
Kat Braybrooke</b><br>Curation & Co-Design Lead<br>Mozilla Foundation<br><br>Email: <a href="mailto:kat@mozillafoundation.org" target="_blank">kat@mozillafoundation.org</a><br>
Twitter/IRC: <a href="https://twitter.com/codekat" target="_blank">@codekat</a><br>
Web: <a href="https://www.webmaker.org/" target="_blank">https://webmaker.org/teach</a></td></tr></tbody></table><br><a href="https://www.webmaker.org/" target="_blank"></a></div><span style="font-family:arial;font-size:small"></span></div>
</div>
<br><br><div class="gmail_quote">On Thu, Apr 3, 2014 at 9:59 AM, Gavin Suntop <span dir="ltr"><<a href="mailto:gavin@mozillafoundation.org" target="_blank">gavin@mozillafoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div>I also think we should encourage general usage – that’s how libraries get stronger!</div><div><br></div><div>The only caveat is that unlike many libraries, Makerstrap is domain specific for the Webmaker ecosystem. If someone uses it for a non-Webmaker project they’ll still get our logo asset for example. Design elements and components are subject to change and not guaranteed to be backward compatible (although we’re striving for it). First and foremost it is designed to solve our internal design consistency needs.</div>
<div><br></div><div>With this caveat in mind, not all pull requests will be accepted. If your project needs something specific, you’re probably going to still have to make the change upstream. Also, if you plan to always use the latest version you can’t just “set and forget”. You’ll need to monitor your project’s integrity with each successive release. If you want to avoid this: <i>use a fixed version</i>. This all might seem fairly obvious to us internally, but we should be sure to communicate it externally as well.</div>
<div><br></div><div>And yeah, like Cassie said, it doesn’t magically take human designers out of the equation. :)</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>G.</div></font></span><div><div class="h5">
<div><br></div><br><div><div><div>On Apr 3, 2014, at 4:32 AM, Cassie McDaniel <<a href="mailto:cassie@mozillafoundation.org" target="_blank">cassie@mozillafoundation.org</a>> wrote:</div><br><blockquote type="cite">
<div style="word-wrap:break-word">This is awesome Kat to see Makerstrap in use like this. I think we should totally encourage this – it's what it's for! Anyone is welcome to file issues <a href="https://github.com/mozilla/makerstrap/issues?labels=design" target="_blank">https://github.com/mozilla/makerstrap/issues?labels=design</a> and especially to contribute fixes to those issues. I think Kate obviously should own whether or not the pull requests get merged with the master, but this is another great avenue for participation if people want to help.<div>
<br></div><div>The other point I might make about Makerstap, and I'm not sure how best to communicate this with the community using it (except perhaps adding a note in the demo or Readme?) that Makerstrap was not built with the intention to eliminate the need for a designer's eye. For example, I can definitely see how the links you pointed out are greatly improved by Makerstrap, but there are still some spacing / padding / layout issues that Makerstrap has a harder time solving for.</div>
<div><br></div><div>So is it for prototyping and quick building? yes absolutely. For quick style wins: yes. But for the finesse and quality and trust built into a professionally designed piece – it's not good for that. Obviously not everyone has access to a professional designer, so this is such a great tool to level in those cases, and perhaps could even help teach better design skills if we had a bit more documentation within Makerstrap.</div>
<div><br></div><div>Another distinction to make is that our team – people who work for Mozilla – should be using Makerstrap but then submitting whatever we make with it (like what you're working on with Fuzzy) for design review. Because we luckily DO have access to real human designers. :) Unless of course it lives in Prototypes.</div>
<div><br></div><div>Does that help answer your questions, Kat? Thanks for raising some great discussion points.</div><div><br></div><div>Cassie</div><div><div>
<div style="font-family:Helvetica;font-size:inherit;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;line-height:1.15;margin-top:0pt;margin-bottom:0pt">
<br><br style="line-height:normal"><span style="line-height:normal">Cassie McDaniel</span><br style="line-height:normal">Webmaker UX/UI Lead</div><div style="font-family:Helvetica;font-size:inherit;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;line-height:1.15;margin-top:0pt;margin-bottom:0pt">
<a href="mailto:cassie@mozillafoundation.org" target="_blank">cassie@mozillafoundation.org</a></div><div style="font-family:Helvetica;font-size:inherit;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;line-height:1.15;margin-top:0pt;margin-bottom:0pt">
IRC & Twitter: cassiemc</div>
</div>
<br><div><div>On 2014-04-02, at 10:05 PM, Brett Gaylor <<a href="mailto:brett@etherworks.ca" target="_blank">brett@etherworks.ca</a>> wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word">Hi, Kat!<div>
<br></div><div>I think you meant to link to one of those tutorials as displayed in Thimble, correct? like this?</div><div><br></div><div><a href="https://thimble.webmaker.org/project/43402/remix" target="_blank">https://thimble.webmaker.org/project/43402/remix</a></div>
<div><br></div><div>And the question is, essentially: </div><div><br></div><div>is there any reason why we shouldn't be encouraging tutorial-authors from our community to use makerstrap?</div><div><br><div><div>On 2014-04-02, at 4:54 PM, Kat Braybrooke <<a href="mailto:kat@mozillafoundation.org" target="_blank">kat@mozillafoundation.org</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div><div>Hey guys, <br><br></div>In the <a href="http://webmaker.org/" target="_blank">Webmaker.org</a> call today we had a discussion about Makerstrap, and how it is proving to be awesome in new and unexpected ways, especially related to the creation of community-built OERs. <br>
<br></div>Here's a sample of how much better it makes the tutorials we are building re look + feel: <a href="https://keyboardkat.makes.org/thimble/kats-event-reporter-tutorial" target="_blank">https://keyboardkat.makes.org/thimble/kats-event-reporter-tutorial</a><br>
<br>And here are two samples of its styling on two new starter resources <a href="https://webmaker.org/starter-makes" target="_blank">https://webmaker.org/starter-makes</a> being built by me + fuzzy, one for reporting on Hive-style events, and one to log group brainstorms during events. <br>
<br><a href="https://keyboardkat.makes.org/thimble/event-reporter" target="_blank">https://keyboardkat.makes.org/thimble/event-reporter</a><br><a href="https://moz-wduyck.makes.org/thimble/thinkbig-brussels" target="_blank">https://moz-wduyck.makes.org/thimble/thinkbig-brussels</a><br>
<div><br></div><div>Given this, how much would you like quick-use styling kits like Makerstrap to be shared widely with our communities, especially Teach the Web focused ones? <br><br></div><div>The pros: It makes starter resources, tutorials and other OERs look great, is easy to explain, and could make mentors' jobs easier in building content.<br>
The cons: It might mean more work for you guys re: maintaining and updating the repo based on community needs and concerns. Alternatively, we could ask community to maintain it together...<br><br></div><div>Would love to hear your thoughts. <br>
</div><div><br clear="all"><div><div><div dir="ltr"><div><a href="https://www.webmaker.org/" target="_blank">
</a>
<table style="font:14px/1.2 'Fira Sans','Open Sans',Helvetica,Arial,Sans-Serif!important">
<tbody><tr>
<td style="border-right:2px solid grey;padding:1em 1em 1em 0px;text-align:center">
<a href="https://www.webmaker.org/" target="_blank">
<img src="http://stuff.webmaker.org/editorial-assets/unnamed.png" style="width:100px" alt="Mozilla Webmaker" height="100" width="100">
</a><br>
</td>
<td style="padding:1em 0px 1em 1em"><b>
Kat Braybrooke</b><br>Curation & Co-Design Lead<br>Mozilla Foundation<br><br>Email: <a href="mailto:kat@mozillafoundation.org" target="_blank">kat@mozillafoundation.org</a><br>
Twitter/IRC: <a href="https://twitter.com/codekat" target="_blank">@codekat</a><br>
Web: <a href="https://www.webmaker.org/" target="_blank">https://webmaker.org/teach</a></td></tr></tbody></table><br><a href="https://www.webmaker.org/" target="_blank"></a></div><span style="font-family:arial;font-size:small"></span></div>
</div>
</div></div></div>
_______________________________________________<br>Webmaker-dev mailing list<br><a href="mailto:Webmaker-dev@mozilla.org" target="_blank">Webmaker-dev@mozilla.org</a><br><a href="https://mail.mozilla.org/listinfo/webmaker-dev" target="_blank">https://mail.mozilla.org/listinfo/webmaker-dev</a><br>
</blockquote></div><br></div></div>_______________________________________________<br>Webmaker-dev mailing list<br><a href="mailto:Webmaker-dev@mozilla.org" target="_blank">Webmaker-dev@mozilla.org</a><br><a href="https://mail.mozilla.org/listinfo/webmaker-dev" target="_blank">https://mail.mozilla.org/listinfo/webmaker-dev</a><br>
</blockquote></div><br></div></div>_______________________________________________<br>Webmaker-dev mailing list<br><a href="mailto:Webmaker-dev@mozilla.org" target="_blank">Webmaker-dev@mozilla.org</a><br><a href="https://mail.mozilla.org/listinfo/webmaker-dev" target="_blank">https://mail.mozilla.org/listinfo/webmaker-dev</a><br>
</blockquote></div><br></div></div></div></div></blockquote></div><br></div>