...
 
Commits (2)
# FNS Structures
This repository is a collection of **learning structures** that are defined and developed by an open community.
This repository is a collection of **learning structures** that are defined and
developed by an open community.
_What are learning structures?_ They are any tools, systems, or techniques that we can use to "structure" our learning.
They are available here for anybody to use, as they wish, within their own learning experiences.
_What are learning structures?_
They are any tools, systems, or techniques that we can use to "structure" our
learning.
They are available here for anybody to use, as they wish, within their own
learning experiences.
_What are some possible examples of learning structures?_
- a system for running online study groups
......@@ -17,12 +23,29 @@ trapped in an institutional "school" context. This repository is intended to be
a context agnostic home for learning structures that anyone can contribute to
and use.
## How do we create new structures?
<!-- markdown-toc start - Don't edit this section. Run M-x markdown-toc-refresh-toc -->
**Table of Contents**
- [FNS Structures](#fns-structures)
- [Motivation](#motivation)
- [How do we create new structures?](#how-do-we-create-new-structures)
- [Step 1. Propose a new structure](#step-1-propose-a-new-structure)
- [Step 2. Test the structure and gather some examples](#step-2-test-the-structure-and-gather-some-examples)
- [Step 3. Format the structure for submission](#step-3-format-the-structure-for-submission)
- [Step 4. Merging In the structure](#step-4-merging-in-the-structure)
- [Step 5. Maintaining the structure](#step-5-maintaining-the-structure)
- [Format](#format)
- [Editors](#editors)
<!-- markdown-toc end -->
# How do we create new structures?
Do you have an idea for a learning structure that you'd like to propose? Anyone is welcome to contribute!
Just follow the steps below:
### Step 1. Propose a new structure
## Step 1. Propose a new structure
If you have an idea for a new structure to help with learning, start by opening
a ~Proposal issue. In it you should describe the structure, how it helps with learning,
......@@ -30,7 +53,7 @@ and how it can be implemented in actual practice. While not mandatory, it's also
recommended that the structure you're proposing is something that: you've actually
used, you're planning to use, or you've observed firsthand (See Step 2)
### Step 2. Test the structure and gather some examples
## Step 2. Test the structure and gather some examples
Structures start with people, and are rooted in actual learning experiences.
In order for a proposal to be adopted into this repository as a new structure,
there needs to be at least one documented example of its use.
......@@ -43,7 +66,7 @@ This is a good way to build out the first examples of a structure's use in the r
Once you've got that in place, it's time to submit the new structure.
### Step 3. Format the structure for submission
## Step 3. Format the structure for submission
You can submit the new structure by opening a ~Proposal Merge Request (MR) in this
repository. The file for the proposed structure should follow the [format](#format)
......@@ -57,13 +80,13 @@ During the review phase the editors will be in communication with you about any
additions, clarifications, or revisions that are needed.
### Step 4. Merging In the structure
## Step 4. Merging In the structure
Once the Structure is ready the editor will assign it a sequential number and merge it
in. At this point it's part of FNS and is available for others to use!
### Step 5. Maintaining the structure
## Step 5. Maintaining the structure
A structure isn't set in stone when it's merged in. Others can contribute
to it and propose changes. As the author you'll be the *maintainer* of the
......@@ -77,7 +100,7 @@ Just keep in mind that it's important for a structure to be well maintained
so that it can continue to provide relevance and value to its community of learners.
## Format
# Format
Each structure is defined in a document written in markdown. Each has:
- a name
......@@ -108,7 +131,7 @@ There are also some suggested sections:
- **References**: a list of references that were used in the structure
## Editors
# Editors
The editors are the ones responsible for maintaining this repository. They
review new structure submissions, manage changes in maintainers, and generally make sure
......