codebar · KimberleyCook · Dec 30, 2025 · Dec 15, 2025 · Dec 15, 2025 · Dec 15, 2025
diff --git a/_includes/sidebar.html b/_includes/sidebar.html
@@ -1,10 +1,11 @@
 <nav>
 	<ul>
-    {% for post in site.posts %}
-      <li>
-        <a class="post-link" href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
-      </li>
-    {% endfor %}
+    {% assign sorted_posts = site.posts | sort: "weight" %}
+{% for post in sorted_posts %}
+  <li>
+    <a class="post-link" href="{{ post.url | prepend: site.baseurl }}">{{ post.title }}</a>
+  </li>
+{% endfor %}
     	<li class="codebar-link"><i class='fa fa-arrow-left'></i><a href="http://www.codebar.io">codebar.io</a></li>
 	</ul>
 </nav>
diff --git a/_posts/2014-12-12-mailing-list-policy.md b/_posts/2014-12-12-mailing-list-policy.md
diff --git a/_posts/2014-12-19-becoming-a-sponsor.md b/_posts/2014-12-19-becoming-a-sponsor.md
diff --git a/_posts/2015-01-31-coordinator-guide.md b/_posts/2015-01-31-coordinator-guide.md
@@ -1,23 +1,24 @@
 ---
 layout: post
 title:  "Coordinator Guide"
+weight: 80
 ---
 
-codebar workshops are a team effort and we really appreciate you wanting to help run things smoother! Here are some tips on how you can help:
+codebar workshops are a team effort and we really appreciate you wanting to help run things smoothly! Here are some tips on how you can help:
 
-- Try to get to the event a little early: 10 minutes or so before the listed start time.
+- Try to get to the workshop a little early: 15 minutes or so before the listed start time.
 
 - Be friendly, positive, and encouraging.
 
-- Try to be close at hand to the front desk where people are being checked in. This is so you are close by to give inductions and help with any required tasks. Once you've finished an induction or helping with something, head back to the front desk.
+- Try to be close to the front desk where people are being checked in. This is so you are close by to welcome people and help with any required tasks.
 
-- Try not to get caught up in conversations unless there are no more inductions or the organisers don't need your help anymore.
+- Try not to get caught up in conversations unless there are no more introductions or the organisers don't need your help anymore.
 
 - Keep an eye for people who are on their own. Talk to them and introduce them to other people.
 
 - If you spot someone without a name badge, chances are they're not checked in. Send them over to the front desk.
 
-- If someone comes to you with a complaint or a concern that you don't know how to address, remember that the rest of the organisers and coordinators have your back and you can always ask for help.
+- If someone comes to you with a complaint or a concern that you don't know how to address, remember that the rest of the organisers have your back and you can always ask for help.
 
 
 ### Coach inductions
@@ -35,11 +36,11 @@ codebar workshops are a team effort and we really appreciate you wanting to help
 
 6. If they are working with a group and are finding it hard (as the students might work at a different pace or need more attention) they should let us know and we will try to find someone to help out.
 
-7. If they need any help or have any concerns, they should speak to a coordinator or organiser.
+7. If they need any help or have any concerns, they should speak to an organiser.
 
-8. If they feel uncomfortable with someone's behaviour, they should bring it to the attention of one of the organisers. It is very important to us that everyone feels safe and comfortable.
+8. If they feel uncomfortable with someone's behaviour, they should bring it to the attention of one of the organisers as soon as possible. It is very important to us that everyone feels safe and comfortable.
 
-9. Thank them for coming. We appreciate their help and any feedback that they may have, as without them we wouldn't be able to have codebar! Let them know that they can get in contact with us at the local chapter's mailing list (e.g. <brighton@codebar.io>).
+9. Thank them for coming. We appreciate their help and any feedback that they may have, as without them we wouldn't be able to run codebar! Let them know that they can get in contact with us at the local chapter's mailing list (e.g. <brighton@codebar.io>).
 
 12. Encourage them to come to the social gathering afterwards, which is a great way to meet new people. They should come.
 
@@ -50,14 +51,14 @@ codebar workshops are a team effort and we really appreciate you wanting to help
 2. How did they hear about codebar? What made them want to come along?
 
 3.  Have they done any development before?
-    -  If yes, what was that? Do they have a goal in mind? (e.g. Are they trying to build their own web app or a portfolio?)
+    -  If yes, what was that? Do they have a goal in mind? (e.g. Are they trying to build their own website or a portfolio?)
 
 4. Are you a student? Speak to them about your experience and how programming has changed things for you.
 
 5. Typing can be hard, but it's very important when learning to code. Type everything and DO NOT copy and paste.
 
 6. codebar is not just about learning to code but also about making friends and meeting people with similar goals. Encourage them to chat to other people and come to the social gathering afterwards.
 
-7. If they need any help they should look for a coordinator or organiser.
+7. If they need any help they should look for an organiser.
 
-8. If they feel uncomfortable with someone's behaviour, they should bring it to the attention of one of the organisers. It is very important to us to ensure that everyone feels safe and comfortable.
+8. If they feel uncomfortable with someone's behaviour, they should bring it to the attention of one of the organisers as soon as possible. It is very important to us to ensure that everyone feels safe and comfortable.
diff --git a/_posts/2015-02-03-our-values.md b/_posts/2015-02-03-our-values.md
@@ -1,14 +1,15 @@
 ---
 layout: post
 title: "Our values"
+weight: 10
 ---
 
 * **codebar is friendly and encouraging**. The atmosphere should be one of co-operation and non-judgement. People should help each other out, peer-to-peer.
 
-* **codebar is accessible.** All codebar workshops are free.
+* **codebar is accessible.** All codebar workshops and events are free.
 
 * **codebar aims to help people learn from scratch.** We want our students to understand why and how things work. We want to teach them the basics and encourage them to practise a language before jumping into frameworks. We are not here to configure a blog or a server, nor to support a project. We want to help students learn how to do this on their own.
 
 * **codebar exists to help the students**. Any giveaways or special offers are only made available to our students. We don't act as a mailing list for our coaches to promote their services unless there is a direct impact in helping promote diversity in the tech industry or teach people programming for free.
 
-* **codebar is open source**. Everyone is welcome to help. All of our workshops are organised and run by volunteers. Our [website](https://github.com/codebar/planner) and [tutorials](https://github.com/codebar/tutorials) are open source. If you have some time we would really appreciate your help! If you can't find any open issues that you can work on, send us an email to <hello@codebar.io> we'll be able to find something :)
+* **codebar is open source**. Anyone is welcome to help. All of our workshops are organised and run by volunteers. Our [website](https://github.com/codebar/planner) and [tutorials](https://github.com/codebar/tutorials) are Open Source. If you have some time we would really appreciate your help! If you can't find any open issues that you can work on, send us an email to <hello@codebar.io> we'll be able to find something :)