Refactor the guidebook as Markdown-first

CONTRIBUTING.md

@@ -3,6 +3,31 @@
 We aim to make contributing to The Open Source Way a pleasant and enriching experience for all project participants, and we welcome contributions of all kinds.
 
 ## Getting started
+This project uses Markdown and a git-based workflow. We track editorial, technical, governance, and marketing discussions on [their respective project boards](https://github.com/theopensourceway/guidebook/projects).
+
+Each chapter is a Markdown file that is associated with an issue.
+The chapter contains its own outline, content, and lexicon.
+
+Each section is folder that contains files of chapters for that section.
+Each section has one or more chapters in it.
+There is not an issue associated with a section, unless a new section is being created.
+
+Want to get involved?
+
+Come talk with us on [the mailing list](https://lists.theopensourceway.org/admin/lists/contrib.theopensourceway.org/) and see [CONTRIBUTING.md](https://github.com/theopensourceway/guidebook/blob/master/CONTRIBUTING.md) to learn how to make your first contribution.
+
+## Community architecture
+For the 2.0 refresh, we've defined a set of roles and responsibilities around an initial, core group of contributors most familiar with the goals of the project. Beyond that, we'll evolve with the participation of new contributors and update [CONTRIBUTING.md](https://github.com/theopensourceway/guidebook/blob/master/CONTRIBUTING.md) to reflect current contribution guidelines.
+
+At the moment:
+
+* Project Lead Karsten Wade (@quaid) is responsible for providing vision and leadership to evolve from his original 1.0 work
+* Lead Editor Brian Proffitt (@bproffitt) is responsible for leading a team of editors to work with multiple authors and content sources toward a cohesive, highly readable guide
+* Lead Writer Shaun McCance (@shaunix) is responsible for working directly with writers to shape their content into the level, style, and narrative of the overall guide
+* Editing team (Brian Proffitt, Karsten Wade, Shaun McCance) is responsible for polishing and integrating submissions to ensure consistency of quality and voice
+* Writing team (Bryan Behrenshausen (@semioticrobotic), Brian Proffitt, Karsten Wade, Shaun McCance) is responsible for composing, collecting, and otherwise curating materials included in the guidebook.
+
+## Contribution process
 
 ### 1. Review outstanding issues
 

CONTRIBUTORS.md

@@ -0,0 +1,58 @@
+# Contributors
+
+## Chapter authors
+
+* Introduction: Presenting The Open Source Way
+  * Author(s): [Karsten Wade](mailto:[email protected])
+* Community 101
+  * Author(s): [Bryan Behrenshausen](mailto:[email protected]), [Dave Neary](mailto:[email protected]), [Karsten Wade](mailto:[email protected])
+* New Project Checklist
+  * Author(s): [Lisa Caywood](mailto:[email protected]), [Josh Berkus](mailto:[email protected]), [Bryan Behrenshausen](mailto:[email protected]), [Karsten Wade](mailto:[email protected])
+* Creating an Open Source Product Strategy
+  * Author(s): [Dave Neary](mailto:[email protected])
+* Communication Norms in Open Source Software Projects
+  * Author(s): [Leslie Hawthorn](mailto:[email protected])
+  * Editor(s)/Reviewer(s): [Paula Dickerson](mailto:[email protected]) (lead), Editorial team
+* Building Diverse Open Source Communities by Making Them Inclusive First
+  * Author(s): [Lauren Maffeo](mailto:[email protected])
+  * Editor(s)/Reviewer(s): [Bryan Behrenshausen](mailto:[email protected]) (lead), [Marina Zhurakhinskaya](mailto:[email protected]) (subject matter expert (SME) reviewer), Editorial team
+* Why People Participate in Open Source Communities
+  * Author(s): [Gordon Haff](mailto:[email protected])
+  * Editor(s)/Reviewer(s): [Brian Proffitt](mailto:[email protected]) (lead), Editorial team
+* Incentivizing and Rewarding Participants
+  * Author(s): [Bryan Behrenshausen](mailto:[email protected])
+* From Users to Contributors
+  * Author(s): [Dave Neary](mailto:[email protected])
+* What Is a Contribution?
+  * Author(s): [Karsten Wade](mailto:[email protected])
+* Essentials of Building a Community
+  * Author(s): [Andy Oram](mailto:[email protected])
+* Constructing an Onboarding Experience
+  * Author(s): [Ray Paik](mailto:[email protected]), [Bryan Behrenshausen](mailto:[email protected])
+* Creating a Culture of Mentorship
+  * Author(s): [Karsten Wade](mailto:[email protected]), [Guedis Cardenas](mailto:[email protected])
+* Project and Community Governance
+  * Author(s): [Dave Neary](mailto:[email protected]), [Josh Berkus](mailto:[email protected]), [Bryan Behrenshausen](mailto:[email protected])
+  * Editor(s)/Reviewer(s): [Bryan Behrenshausen](mailto:[email protected]) (lead), Editorial team
+* Understanding Community Roles
+  * Author(s): [Andy Oram](mailto:[email protected]), [Karsten Wade](mailto:[email protected])
+* Community Manager Self-Care
+  * Author(s): [Ashley Nicolson](mailto:[email protected])
+  * Editor(s)/Reviewer(s): [Karsten Wade](mailto:[email protected]) (lead), [Dr. Karen Hixson](https://www.karenhixsonlpc.com/) (subject matter expert (SME) reviewer), Editorial team
+* Defining Healthy Communities
+  * Author(s): [Karsten Wade](mailto:[email protected])
+* Understanding Community Metrics
+  * Author(s): [Ray Paik](mailto:[email protected]), [Brian Proffitt](mailto:[email protected]), [Bryan Behrenshausen](mailto:[email protected])
+  * Editor(s)/Reviewer(s): [Brian Proffitt](mailto:[email protected]) (lead), [Bryan Behrenshausen](mailto:[email protected]), Editorial team
+* Announcing Software Releases
+  * Author(s): [Brian Proffitt](mailto:[email protected])
+
+## Project teams 
+
+### Editorial team
+
+* Brian Proffitt (lead)
+* Shaun McCance (lead writer)
+* Bryan Behrenshausen
+* Paula Dickerson
+* Karsten Wade

LICENSE.md

@@ -1,3 +1,5 @@
+# License
+
 Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
 
 You are free to:

README.md

@@ -1,29 +1,5 @@
-# Guidebook
+# The Open Source Way
 
-This repository contains source materials for [The Open Source Way 2.0](https://www.theopensourceway.org/), a (somewhat opinionated) guidebook for anyone interested in managing open source communities. It collects best practices for initiating, nurturing, growing, and maintaining groups of passionate contributors.
+[The Open Source Way](https://www.theopensourceway.org/) is a (somewhat opinionated) guidebook for anyone interested in managing open source communities.
 
-The Open Source Way 2.0 refreshes [pre-existing materials](https://www.theopensourceway.org/wiki) on these topics.
-
-## Getting started
-
-This project uses AsciiDoc and a git-based workflow. We track editorial, technical, governance, and marketing discussions on [their respective project boards](https://github.com/theopensourceway/guidebook/projects).
-
-Each chapter is an .adoc file that is associated with an issue. The chapter contains its own outline, content, and lexicon.
-
-Each section is an .adoc file that contains the outline of chapters for that section. Each section has one or more chapters in it. There is not an issue associated with a section, unless a new section is being created.
-
-Want to get involved?
-
-Come talk with us on [the mailing list](https://lists.theopensourceway.org/admin/lists/contrib.theopensourceway.org/) and see [CONTRIBUTING.md](https://github.com/theopensourceway/guidebook/blob/master/CONTRIBUTING.md) to learn how to make your first contribution.
-
-## Community architecture
-
-For the 2.0 refresh, we've defined a set of roles and responsibilities around an initial, core group of contributors most familiar with the goals of the project. Beyond that, we'll evolve with the participation of new contributors and update [CONTRIBUTING.md](https://github.com/theopensourceway/guidebook/blob/master/CONTRIBUTING.md) to reflect current contribution guidelines.
-
-At the moment:
-
-* Project Lead Karsten Wade (@quaid) is responsible for providing vision and leadership to evolve from his original 1.0 work
-* Lead Editor Brian Proffitt (@bproffitt) is responsible for leading a team of editors to work with multiple authors and content sources toward a cohesive, highly readable guide
-* Lead Writer Shaun McCance (@shaunix) is responsible for working directly with writers to shape their content into the level, style, and narrative of the overall guide
-* Editing team (Brian Proffitt, Karsten Wade, Shaun McCance) is responsible for polishing and integrating submissions to ensure consistency of quality and voice
-* Writing team (Bryan Behrenshausen (@semioticrobotic), Brian Proffitt, Karsten Wade, Shaun McCance) is responsible for composing, collecting, and otherwise curating materials included in the guidebook.
+It collects best practices for initiating, nurturing, growing, and maintaining groups of passionate contributors.

SUMMARY.md

@@ -0,0 +1,29 @@
+# Table of contents
+
+* [The Open Source Way](README.md)
+* [Introduction: Presenting The Open Source Way](presenting-the-open-source-way.md)
+* [Getting Started](getting-started/README.md)
+  * [Community 101](getting-started/community-101.md)
+  * [New Project Checklist](getting-started/new-project-checklist.md)
+  * [Creating an Open Source Product Strategy](getting-started/creating-an-open-source-product-strategy.md)
+* [Attracting Users](attracting-users/README.md)
+  * [Communication Norms in Open Source Projects](attracting-users/communication-norms-in-open-source-software-projects.md)
+  * [Building Diverse Open Source Communities by Making Them Inclusive First](attracting-users/building-diverse-open-source-communities-by-making-them-includive-first.md)
+* [Guiding Participants](guiding-participants/README.md)
+  * [Why People Participate in Open Source Communities](guiding-participants/why-people-participate-in-open-source-communities.md)
+  * [Incentivizing and Rewarding Participants](guiding-participants/incentivizing-and-rewarding-participants.md)
+* [Growing Contributors](growing-contributors/README.md)
+  * [From Users to Contributors](growing-contributors/from-users-to-contributors.md)
+  * [What Is a Contribution?](growing-contributors/what-is-a-contribution.md)
+  * [Essentials of Building a Community](growing-contributors/essentials-of-building-a-community.md)
+  * [Constructing an Onboarding Experience](growing-contributors/constructing-an-onboarding-experience.md)
+  * [Creating a Culture of Mentorship](growing-contributors/creating-a-culture-of-mentorship.md)
+  * [Project and Community Governance](growing-contributors/project-and-community-governance.md)
+  * [Understanding Community Roles](growing-contributors/understanding-community-roles.md)
+  * [Community Manager Self-Care](growing-contributors/community-manager-self-care.md)
+* [Measuring Success](measuring-success/README.md)
+  * [Defining Healthy Communities](measuring-success/defining-healthy-communities.md)
+  * [Understanding Community Metrics](measuring-success/understanding-community-metrics.md)
+  * [Announcing Software Releases](measuring-success/announcing-software-releases.md)
+* [Contributors](CONTRIBUTORS.md)
+* [License](LICENSE.md)