mybb · JordanMussi · Jan 1, 2018 · Jan 8, 2018 · Jun 9, 2019 · Jun 9, 2019
diff --git a/october-2017/17.md → 2017-10/a-fresh-perspective.md b/october-2017/17.md → 2017-10/a-fresh-perspective.md
@@ -1,4 +1,6 @@
-![Blog header image](./17-head.jpg)
+# A Fresh Perspective
+
+![image](./a-fresh-perspective/head.jpg)
 
 MyBB has been making some changes lately, and if you haven't noticed we're here to give you the scoop. Discussion about bridging 1.x closer to 2.0 has been settling, and as such we have decided on the best course of action moving forward. This comes with some other updates, including the main site going responsive, our blog getting way more fun, setting up an official demo site, and speeding up that darn extension approval process.
 
@@ -45,7 +47,7 @@ We're also considering the possibility of adding thread prefixes to the Requests
 ### MyBB Software Development Path
 After a lot of discussion internally, on the forum and in Discord, we've decided on the path that the MyBB software will be following leading up to MyBB 2. While we can all agree that MyBB needs to be more modern, rewriting it entirely from scratch is an enormous task and is taking much longer than we anticipated. Judging from the input from users, as well as discussion among staff, our best option moving forward will be to further bridge the 1.x series toward MyBB 2, while updating it to be more usable and modern.
 
-![MyBB Poll results](./17-screen.png)
+![MyBB Poll results](./a-fresh-perspective/screen.png)
 
 We have not decided on any specifics, but have discussed some of the following options:
 * Use Twig

diff --git a/october-2017/17-head.jpg → 2017-10/a-fresh-perspective/head.jpg b/october-2017/17-head.jpg → 2017-10/a-fresh-perspective/head.jpg
diff --git a/october-2017/17-screen.png → 2017-10/a-fresh-perspective/screen.png b/october-2017/17-screen.png → 2017-10/a-fresh-perspective/screen.png
diff --git a/november-2017/docker.md → 2017-11/docker.md b/november-2017/docker.md → 2017-11/docker.md
@@ -1,4 +1,4 @@
-### Released: MyBB 1.8 Dockerfile & Docker Compose Recipe
+# MyBB 1.8 Dockerfile & Docker Compose Recipe
 
 With the recent announcements of the 1.10 branch we've also got some great news for both plugin developers and theme designers. In recent weeks, work has been underway to create an official Docker image for the MyBB 1.8 series. This work has been taken on by a community member who proposed such a solution and set to work on getting it done. Also provided within the repository are two example `docker-compose.yml` files, to be used with Docker Compose or Swarm. Docker is a technology for creating lightweight containers to manage and orchestrate software. It works across multiple platforms, and makes it easy to quickly get a live instance of the current MyBB version running with a variety of different configurations without requiring much effort to install database management systems and such on your machine. Docker is a brilliant tool for developers to quickly prototype ideas in a fresh, consistent environment. You can find out more information on Docker [here](https://docs.docker.com/get-started/).
 

diff --git a/december-2017/php-version.md → 2017-12/php-version.md b/december-2017/php-version.md → 2017-12/php-version.md
@@ -1,4 +1,4 @@
-### Minimum Supported PHP Version for Upcoming MyBB Releases
+# Minimum Supported PHP Version for Upcoming MyBB Releases
 
 When MyBB 1.8 was released in September 2014, it required a PHP version 5.2 or greater while the previous series, MyBB 1.6 (originally released 3rd August, 2010), required PHP 5.1 or greater. To put that into perspective, PHP 5.2 was released on 2nd November, 2006 and on 6th January, 2011 was declared end of life (End Of Life: meaning it will not receive any updates nor security fixes). So before MyBB 1.8 was even released, it was supporting PHP versions that had long since been marked end of life by the PHP Group.
 

diff --git a/january-2018/support-policy.md → 2018-01/support-policy.md b/january-2018/support-policy.md → 2018-01/support-policy.md
diff --git a/february-2018/2.0-on-hold.md → 2018-02/2.0-on-hold.md b/february-2018/2.0-on-hold.md → 2018-02/2.0-on-hold.md
diff --git a/june-2018/demo-board.md → 2018-06/demo-board.md b/june-2018/demo-board.md → 2018-06/demo-board.md
diff --git a/july-2018/1.9-dev-update-2.md → 2018-07/1.9-dev-update-2.md b/july-2018/1.9-dev-update-2.md → 2018-07/1.9-dev-update-2.md
diff --git a/README.md b/README.md
@@ -1,3 +1,27 @@
-# MyBB Blog Drafts
+[![MyBB](https://raw.github.com/mybb/mybb/feature/images/logo.png "MyBB")](https://mybb.com "MyBB")
 
-This repository is used to manage and prepare blog posts for the [MyBB Blog](https://blog.mybb.com).
+# MyBB Development Blog Drafts
+
+This repository is used to manage and prepare blog posts for the [MyBB Development Blog](https://blog.mybb.com).
+
+## Drafting a post
+
+A member of the team will create a new branch from `master` in this repository (not a fork), named with a *short* title for the post using [kebab-case](https://en.wikipedia.org/wiki/Letter_case#Special_case_styles).
+
+The initial draft will be made by creating a new file using the same short title with a `.md` extension in the appropriate `YYYY-MM` directory.
+
+The intended long title will be used as a main heading in the markdown file, allowing suggestions to be made, followed by the main body of the post.
+
+```markdown
+# Long title
+
+...body
+```
+
+Note that the post should not be signed off at the end of the body.
+
+After committing the intial draft and pushing the branch a Pull Request will be made to `master` where discussion and suggestions can take place. Large suggested changes can be made by the community by creating Pull Requests to the draft branch.
+
+## Merging a draft into master
+
+When a draft is merged into `master` it simply means that it is in an acceptable form to be published. This does not mean that the post will be published on the blog immediately and other changes can still be suggested.