fixing markdown syntax (#276)

Author: GarthDB

articles/_posts/2013-09-25-the-open-source-design-manifesto.md

@@ -18,7 +18,7 @@ Here's the original manifesto:
 
 Here's a text-based version for all the bots out there (with some slight modifications for clarity):
 
-##Open Source Design Manifesto
+## Open Source Design Manifesto
 
 I will:
 

articles/_posts/2013-10-31-open-design-is-not-design-by-committee.md

@@ -12,29 +12,29 @@ As I've chatted with designers about the idea of working in the open and allowin
 
 For those who are unfamiliar with the term Design By Committee, it is a special kind of hell for designers who find themselves working on a project with too many stakeholders. Often times this causes a project to pivot in seemingly random directions as committee members compromise on divergent opinions.
 
-##Misunderstanding of the Term Open Source
+## Misunderstanding of the Term Open Source
 
 I think some designers have the mistaken idea that open source projects are lawless anarchies, where random contributors haphazardly throw bits and pieces together; forming a version of Frankenstein's monster that hopefully can perform basic tasks. In reality a healthy open source project needs to have an owner, or small group of owners[^1], with a strong sense of where the project is heading. With a core team in place, outside contributors can file issues, submit contributions, and just complain about things they don't like. The core team of owners can then accept or reject the contributions from the community (hopefully in a way that encourages growth and future contributions).
 
->Instead of being an expert consultant, the designer becomes the tool of the committee members who often have very little design experience
+> Instead of being an expert consultant, the designer becomes the tool of the committee members who often have very little design experience
 
-##Ownership is key
+## Ownership is key
 
 The most important difference between Open Source Design and Design by Committee is this concept of ownership. In the context of Design by Committee, usually the designer is a contractor or agency hired by the committee, or underling that is far below the committee members on the org chart. This is the heart of the problem with designing by committee; instead of being an expert consultant, the designer becomes the tool of the committee members who often have very little design experience. It is not unlike giving a formula one racecar to someone without a driver's license; regardless of how well the car can perform, the result will most likely be unremarkable or even disastrous.
 
 In the case of Open Source Design, not all contributors and community members are equal, but all involved should be designers. The owner of the project is the lead designer the majority of the time, and when contributions come in, switches to role of creative director. They should help to shape contributions to fit into the overall purpose of the project, or reject them outright with clear reasoning.
 
-##That Sounds Like a Lot of Work
+## That Sounds Like a Lot of Work
 
 I can't lie and say that it isn't, but community contributions, in the form of issues filed or pull requests submitted, are just another form of design criticism, and criticism is an essential part of any design process. It is possible that the owner will have to deal with more feedback than expected, but this collision of ideas will open opportunities for real innovation. It is also important to know that anytime the discussion is moving past the point of useful collaboration, the owner should not hesitate to shut it down and get back to work.
 
-##What Happens if the Project Owner is a Tool?
+## What Happens if the Project Owner is a Tool?
 
 It can happen. As ideas collide in a discussion, it is possible that contributors will feel the need to move in a different direction than the owner's goals. In an open source project with the right kind of license, the rebelling faction should have the option of forking the project and continuing independently. This is not a great outcome in terms of community development, but it gives an owner with dictatorial tendencies a reason to work with others.
 
 >The Open Source workflow benefits all parties involved
 
-##Why do it?
+## Why do it?
 
 When implemented correctly, the Open Source workflow benefits all parties involved. Contributors get a chance to collaborate with designers in a more autonomous capacity than most work environments allow, and still receive feedback and encouragement from the project owners. The owners get outside opinions to challenge their assumptions and sometimes they get fantastic contributions worth all the hassle. Most importantly, all the designers involved have the privilege of improving the design community and building something they care about.
 

articles/_posts/2013-12-06-the-roadmap.md

@@ -9,7 +9,7 @@ excerpt: Someone in the IRC asked how they could contribute and what our roadmap
 ---
 Someone in the IRC[^1] asked how they could contribute and what our roadmap is.  I thought I would lay out a few places where anyone could jump in if they wanted to help out.
 
-##Authors Wanted
+## Authors Wanted
 
 Feel free to write about anything related to open source and design and how designers can get involved.  [Areus Wade](https://twitter.com/areus) wrote a great post on [how to contribute a post to the blog](/articles/how-to-contribute/).
 
@@ -54,7 +54,7 @@ If you need a place to start we have a running list of topics in the [github iss
 
 <ul id="article-issues"></ul>
 
-##Designers Wanted
+## Designers Wanted
 
 This is a site about open source design, and has a definite lack of design going on here.  The easiest way to jump in is to comment in the [design discussions](https://github.com/designopen/designopen.github.io/issues?direction=desc&labels=design+discussion&page=1&sort=updated&state=open):
 
@@ -68,7 +68,7 @@ You can do any part of it: just visual design, or actual coding.  [One post](/ar
 
 The idea is each post should be unique, so there is no style guide to follow; make your own.
 
-##Resource Seekers Wanted
+## Resource Seekers Wanted
 
 Sorry, resource seeker sounds lame, but I couldn't think of a more elegant want to put it.  We have a running list of resources and examples of open source design.  Feel free to tweet [@designopen](http://www.twitter.com/designopen) if you have anything you'd like to add.
 

articles/_posts/2014-03-31-whats-next.md

@@ -18,15 +18,15 @@ First the questions:
 
 Let's break these down.
 
-###1. What do you want to do?
+### 1. What do you want to do?
 
 This deals primarily with the professional context, but it could apply to any area of your life.  It isn't a trick question though, what do you want? What is on your dream to-do list? Maybe it's to write a book, speak at a specific conference, learn a new skill, get a new position, or be hired by a specific company.
 
 We should be happy with the good things we have going for us in our lives, but we should never stay standing still. Push yourself to want something more. I'm not necessarily recommending you should quit your job (yet) and try to form a startup tomorrow, but if that's what you want to ultimately do you should keep that goal in mind.
 
 Write it down if it'll help you think it through.
 
-###2. What are you lacking?
+### 2. What are you lacking?
 
 It's not hard to think about this question.  Often self doubt pushes our weakness to the forefront of our mind, so maybe work through this with a trusted friend.
 
@@ -36,7 +36,7 @@ Take this to-do list of skills and with that close friend, try to make an honest
 
 This question is not designed to depress you. If you stop here I'd be doing you a diservice, so stick with it to the end.
 
-###3. How can you bridge that gap?
+### 3. How can you bridge that gap?
 
 Now that you have your dream board done, start figuring out what you need to do to get to where you are dreaming. For most situations you'll need to work on a showcase project, both to learn a skill and also to demonstrate your prowess.
 
@@ -48,7 +48,7 @@ So pick a project. For most cases the project should be:
 * **collaborative**.  This is a bit of a bonus, but if possible you will grow fastest and in the right direction if you have a mentor helping to light the path ahead of you.
 * something you are **passionate** about.
 
-##The Simple Proposal
+## The Simple Proposal
 It shouldn't be too surprising, but I would propose that you should consider an open source project, either an existing one or start a new project.  If you can find a way to do some of these growing projects as part of your day job, more power to you, but it's not common that your goals perfectly coincide with those of your employer.
 
 If you are looking for a mentor, [I volunteer](https://38.media.tumblr.com/b3ce9009a678f4cb4a040c959a7a50d7/tumblr_mun46pEkbT1sjav2eo3_500.gif).  I'm not perfect, or the expert in all things, but I believe firmly in the role of mentorship in the process of progression, so I'm putting my money where my mouth is.  Reach out to me on [Twitter](http://www.twitter.com/garthdb) or leave a comment below.

articles/_posts/2014-04-07-being-stylish.md

@@ -14,7 +14,7 @@ At the time the site's design was about 4 CSS rules away from default. I remembe
 
 Well it worked, and less than a week later I stepped in and worked on it.
 
-##Design vs Style
+## Design vs Style
 
 Early in the process, and through conversation with Garth the decision was made to avoid *designing* the site,
 instead choosing to *style* it. This site is set up so that any article can (and hopefully will) get its own
@@ -23,7 +23,7 @@ design treatment. A fantastic example can be seen on the article [*USING GITHUB
 With that in mind, the goal for this iteration of the look of the site became
 "Nice, but still something someone would want to replace."
 
-##A Checklist
+## A Checklist
 
 A list of requirements was drawn up for the default design of the site:
 

articles/_posts/2014-09-29-open-source-design-is-now-design-open.md

@@ -11,7 +11,7 @@ tags: annoucement featured news
 
 Thanks to some timely posts to our [GitHub issue on branding](https://github.com/DesignOpen/designopen.github.io/issues/33#issuecomment-56763448) we decided to rethink the name of this project. Originally I planned for the site to be a definitive guide on what open source design is, hence the original domain name, opensourcedesign.is, but that has become too limiting for the direction this project is heading. Instead we are moving to a call for action: *Design Open!*
 
-##The Difference between Open Design and Open Source Design
+## The Difference between Open Design and Open Source Design
 
 To work on open source design means to publish creative work with an open license, giving the community a chance to reuse and rework your content in ways you may not have considered. It is also the act of contributing design work to existing open source projects. Both  executions of open source design imply that the work is open to contributions and collaboration from outside designers.
 
@@ -21,6 +21,6 @@ As an added benefit to designing in the open, it is a short leap to open source
 
 The removal of the term open source from the name of this project does not signify we are going to stop encouraging designers to open source their work, or to collaborate on open source projects. On the contrary, we want to encourage all designers to become familiar with open source and make contributions to projects they care about.
 
-##The Call
+## The Call
 
 A while ago this site hit the front page of [Designer News](https://www.designernews.co/stories/8313-open-source-design-using-layervault) and the traffic spiked dramatically. It was wonderful to get the exposure, but ultimately I found it a little disappointing that it didn't lead to any significant, trackable increase in discussion. This is not merely a nice idea, it is a clarion call to shed our insecurities, pride, and paralyzing perfectionism; to dedicate effort to helping worthy causes; and to raise the quality of design and design education on the web. A call to design open.

articles/_posts/2015-02-25-open-study.md

@@ -7,13 +7,13 @@ priority: 1
 tags: ux study featured
 excerpt: An attempt to obtain more data about how designers can and do work on open source projects.
 ---
-##MOAR DATA!
+## MOAR DATA!
 
 Open Design started as a series of discussions, or maybe a single discussion when different people at different times. I spent time talking to designers and developers at conferences and it usually started with the question: "why aren't more designers doing open source?" Eventually this would lead to other questions like: "what does open source design look like?", "do designers need to learn to code or git to participate?", "does it have to be open source, or just open design?", etc.
 
 These questions led to some article ideas and ultimately the Open Design project. However, these articles are based on anecdotal evidence and theories, which is fine to continue the conversation on the topic of open design, but they lack solid data.
 
-##A Call for Help
+## A Call for Help
 
 Recently we had some new contributors, ([Paulina Durán](http://twitter.com/winterdamsel), [Alicja Salamon](http://alicjasalamon.com/), and [Jan Dittrich](http://twitter.com/simulo)) join our project who want to tackle this issue of research. They have been setting up interviews with designers and developers to learn more about their opinions and workflows. Most of their participants have been in Europe and we'd like to get more diverse participants.