|
@@ -8,17 +8,11 @@ Whether your community is already up and running or still just an ambition, choo
|
|
|
|
|
|
**Describe the reality, not the ideal.** Start with where you are. If your community values democracy but currently runs as an autocracy, own up to it in your Rule. You might also include in your Rule the intention of changing in the future. But sometimes the best way to spur change is to hold a mirror up to how the community is presently operating. Start by describing briefly and clearly how your community operates now.
|
|
|
|
|
|
-**Get that? Be brief.** The longer your Rule is, the more likely you'll be to confuse people and introduce internal inconsistencies.
|
|
|
+**It may be easiest to start with a [template]({% link templates.md %}), but you can also [start from scratch]({% link create.md %}).** On a template, press the <span class="pushButton">Fork</span> button at the bottom to get started. Even if you end up changing almost everything you find in a template, the process can spur thinking in ways that a blank canvas would not.
|
|
|
|
|
|
-**It may be easiest to start with a [template]({% link templates.md %}), but you can also [start from scratch]({% link create.md %}).** On a template, press the <span class="pushButton">Customize</span> button to get started. Even if you end up changing almost everything you find in a template, the process can spur thinking in ways that a blank canvas would not.
|
|
|
+**Drag and drop modules to design your Rule.** Under the community name and basic structure, you can start dragging pre-defined or custom modules into your Rule. You can drag a module into another module to show how the parent module works in greater detail.
|
|
|
|
|
|
-**There are two ways to build a Rule: modules or questions.** Under the community name and basic structure, you can start dragging pre-defined or custom modules into your Rule. Access them via the <span class="pushButton"><img src="{% link assets/tabler_icons/tool.svg %}" title="Modules" /></span> button. Below that, there are a series of questions. Press the <span class="pushButton"><img src="{% link assets/tabler_icons/chevrons-down.svg %}" title="Expand" /></span> buttons to see the questions in each section.
|
|
|
-
|
|
|
-**Don't need fill in any more than you feel you need to.** If you leave anything blank, the field will simply disappear when you publish.
|
|
|
-
|
|
|
-**If you use the modules, be sure to explain what they mean.** When you add a module or click on its name, a field appears that allows you to describe the module in your own words. Text typed there automatically becomes part of the module, and it will appear when you hover the cursor over its name. For inspiration, you can press the icon on pre-defined modules to learn more about it.
|
|
|
-
|
|
|
-**If you use the questions, answer them in complete sentences.** The questions will disappear when you publish. Make sure what you write will make sense when the questions are no longer there.
|
|
|
+**If you use the modules, be sure to explain what they mean.** When you add a module or click on its name, a field appears that allows you to describe the module in your own words. Text typed there automatically becomes part of the module, and it will appear when you hover the cursor over its name. For inspiration, you can press the  icon on pre-defined modules to learn more about them.
|
|
|
|
|
|
**Separate the Rule from its data**. Think of your Rule like a constitution as opposed to a code of laws, like a building as opposed to the people who put it to use. Don't try to include all your community's policies in your Rule; explain there how you make and change policies. Don't list out who holds what roles; just define the roles. In your Rule, make clear where people can find that data---the policies, the role-holders, and so forth.
|
|
|
|