THE MUDDLE WORKFLOW
Creating and collaborating is our primary goal in the MUDDLE Backyard. To do this we must have MUDDLErs in the sandbox. We believe that [m]any path[s] to the sandbox foster[s] a neighborly workspace that does not hinder the creative process but instead offers a greater chance of finding a workflow and network of neighbors that aligns with each MUDDLErs' unique playtime experience. Plus, come Spring there will be a wealth of MUDDLE to sift through as we move things into the house for publication in the mag.
Path One: MUDDLE from Command Line ⭐
Path Two: MUDDLE from GitHub 
Path Three: MUDDLE from GitHub Desktop 💻
Check House Styles.
MUDDLErs we're here to help. We have laid out our community standards in House Styles - such as file naming conventions
Pin to the NeighBBoard.
Inside of the sandbox the best neighbors share their journeys of sandy stories and art supplies. When editors notice your additions to the sandbox or NeighBBoard include a look into your process we'll label your pull request or backyard discussion (issue on issues board) with the neighBBoard label.
MUDDLErs are encouraged to ask - "Won't you be my neighbor?" Whether writing a comment when submitting a pull request or starting discussions in our backyard you can be sure you'll always have a neighbor. As editors and creators, we strive to make playtime fun but understand accidents happen. Just ask for help and we will label your pull request or issue with the first-aid label ensuring you g{e|i}t the help you need while signaling to others that might also be struggling.
The first step to habituation is trying and messing up. We learn better ways to approach new tasks from past mistakes: our own and others'. Let's build your community and g{e|i}t you started by customizing your FORK.
