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 💻
Pin to the NeighBBoard.
Inside of the sandbox the best neighbors share their journeys of sandy stories and art supplies. Let us know your additions to the sandbox include a look into your process by labeling your pull request 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 artists, we strive to make playtime fun but understand accidents happen. Just ask for first-aid by labeling your pull request or issue with the first-aid label.
The first step to habituation is failure. We learn better ways to approach new tasks from past mistakes: our own and others'. Invite neighbors to your backyard by sharing unique README.md files for each of your works ✏️ or by developing your own Techtual Condition wiki 📑. Let the community know where to find your other versions of self (social media, works published elsewhere, etc.) by creating a README.md file in your creator folder in the sandbox.