Netlify CMS Instructions
This documentation covers using Netlify CMS to write content for the Open Practice Library. At a high level the workflow is fairly simple:
- On a practice page or the home page hit the
Add newbutton to launch the CMS.
- Login with your GitHub Account. (If you don’t have an account you can create one here. Don’t worry, it’s free to create an account!)
- Once logged into the CMS, pick the
How Toguide you want to implement or improve.
- Update it with your changes and remember to append your
githubusername to the end of the authors list.
- Make your changes and hit
Save. The moderators will pick up the changes from there!
For even more details on these, see the guides below for Content Writers and Content Moderators:
Adding or updating practices (Content Writers)
If you’re new to the CMS and have not created content before; there are two things you need to do before creating content
- To create or edit a practice, you will need a Github account. You don’t need to have any content in Github as it is only used for authentication purposes.
- With a Github account created add your author information to the CMS by filling in the fields (only name and gitusername are mandatory). Hit save and this will create a Pull Request to add your author into the Git repository.
Before you continue, please check the Pre-Requisites above (for example, that you have a valid GitHub.com account)
We are using Netlify CMS to update this content.
- Visit Netifly Admin Page and click “Login with Netifly Identity”.
- Select “Continue with GitHub” and enter your Github credentials.
- Click “New Practices”.
- Fill in the Title with the name of your Practice and the subtitle with something catchy to describe your content. Leave the publish date as is.
- To include a splash image for your practice add one to the Jumbotron
- Add a tile icon image to the practice for it to appear on the homepage.
- Add your
Githubusername to the list of Authors to get a writers credit.
- From the Mobius dropdown select where your article fits
- You can either use Rich Text or Markdown format for the content. Rich Text could be easier for non-technical people and you can use the style icons at the top of the Body section to add headers and formatting.
Once you have added your content, click the blue “Save” button at the top of the screen.
Change the Status to “In Review”.
This will raise a pull request on the underlying Github repository which can then be actioned by one of the site moderators.
If you try to publish the Practice yourself, you will see an error as it needs to be curated by a moderator.
You will receive emails once the content has been actioned.
These actions could be to add/change or content if everything is good, you will receive and email saying that the content has been merged (accepted in to the library).
You can use the first steps in the above workflow to edit content. Select the practice you wish edit. Don’t forget to update the date and click “Save” once you have edited the content.
An email will be sent to the moderators who will approve the change.
Guidance for Content Writers
A practice must be
- Empowering - It helps teams discover and deliver iteratively.
- Concise - It can be read in a few minutes.
- Agnostic - It doesn’t require the team to follow a specific project management framework.
- Proven - It has been tested in the real world by the practice author.
A practice should be
- Approachable - It can be understood by someone who’s not an expert in project management.
- Visual - It includes images and videos.
- Accessible - It includes alt text for images and captions for videos.
- Novel - It isn’t already covered by another practice.
- Deep - It provides links to related resources, examples, and other materials for readers who want to explore further.
A simple template is shown below which contains some example headers for use when creating a new
Practice within the Library.
|What is it?||A brief description of the practice|
|Why use it?||A short paragraph describing the use case(s) for the use of this practice.|
|How does it fit?||Relevant section(s) of the Open Practice Library for which this practice can be used|
|Related Practices||Which practices can be used in conjunction, before or after this practice|
If you are creating a
How to or facilitation guide, some additional fields need to be filled out in the CMS such as the difficulty of the exercise and the people required to run the session. Some example headings for a How to guide should include, but are not limited to, the following
|What is it?||A brief description of the practice|
|Materials Needed||What materials are required to run the practice? For example, a large whiteboard, sticky notes, whiteboard markers etc|
|Steps||Short, concise description of the things needed to accomplish the goal of the activity. Pictures and videos included in here will really help.|
|Templates||Any reference material such as canvas or other printouts needed|
|External Examples||Any external resources or use cases, blogs etc that can help learners who want to learn more|
Publishing Content (Moderators)
As a moderator, you will receive and email to say that new content has been added:
Automatically generated by Netlify CMS You can view, comment on, or merge this pull request online at: https://github.com/openpracticelibrary/practice-library/pull/9 Commit Summary Create Practices “chrisj-test-of-workflow” File Changes A content/practices/chrisj-test-of-workflow.md (5) Patch Links: https://github.com/openpracticelibrary/practice-library/pull/9.patch https://github.com/openpracticelibrary/practice-library/pull/9.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.
Steps to fix
- Go to the Pull Request Page and click on the relevant pull request or follow the link in the email.
- To see what has been added / changed, go to the “Files changed” tab.
- If you require more information or would like changed to be made, write the comment in the “Leave a Comment” box.
Note: Add @username in the comment so the originator receives the email. The originators user name can be found in the “Commits” tab.
- If you are happy with the content and there are no conflicts, click the “Merge pull Request” button followed by the “Confirm Merge” button. Add some additional comments if required.
- Once merged, delete the branch (this will hopefully be automated at some point) as there is an issue with the CMS that does not allow people to create further edits while it still exists. Click the “Delete Branch” button on the PR’s page.
- This act will deploy the changes to the
stagingenvironment. To deploy the change to the main site, raise a PR from
master. On GitHub, navigate to the
stagingbranch which should be ahead of
masterand hit raise PR. Merge the change set as you did before.
- If you go back to the List of Practices you should see the newly added practice.
Note: The order is a little quirky at the moment - not sure why. It’s mainly alphabetical with a few exceptions.