Skip to content

THE MUDDLE WORKFLOW

Rebecca Parker edited this page Nov 9, 2018 · 78 revisions

Go to the backyard and play!

One of our primary goals, as editors, is to get MUDDLERS into the sandbox: creating and collaborating. We believe that having many paths to the sandbox fosters a neighborly workspace that does not hinder the creative process but instead offers a greater chance of finding a workflow that aligns with each MUDDLERS' unique playtime experience.

Choose your path.

Path Two: MUDDLE from GitHub :octocat:

Path Three: MUDDLE from GitHub Desktop 💻

Share your experience with [the][our] neighborhood.

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.

Pass Notes.

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.

Can we come over?

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 other MUDDLErs 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.

Travel Guide

Home
Muddle Workflowscontribute today!
Our "Techtual" Condition
Why Muddle?a poetic plea


Please note, most icons provide a bit more info — so click and see!

Clone this wiki locally