codebar · ck1ldn · Dec 15, 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,6 +1,7 @@
 ---
 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:

diff --git a/_posts/2015-02-03-our-values.md b/_posts/2015-02-03-our-values.md
@@ -1,6 +1,7 @@
 ---
 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.

diff --git a/_posts/2015-02-05-organiser-guide.md b/_posts/2015-02-05-organiser-guide.md
@@ -1,6 +1,7 @@
 ---
 layout: post
 title: "Organiser Guide"
+weight: 30
 ---
 
 ### Workshops
@@ -63,7 +64,7 @@ If you have a lot of attendees, then you might need multiple organisers to help
 
 Encourage them to come to any social events following the workshop. Usually people don't get that much time to interact at the events and this enables them to expand their tech social circle, find out about opportunities and meet like-minded people.
 
-Make sure to send a thank you tweet/instagram ETC to the host, with a photo from the workshop attached.
+Make sure to send a thank you social media post, be sure to tag the host, and include a photo from the workshop attached.
 
 ## Dealing with problems
 

diff --git a/_posts/2015-02-06-bringing-codebar-to-your-area.md b/_posts/2015-02-06-bringing-codebar-to-your-area.md
@@ -1,19 +1,20 @@
 ---
 layout: post
 title: "Bringing codebar to your area"
+weight: 100
 ---
 
 ### Do you want to bring codebar to your city?
 
 - Part of our goal is to enable people to easily start a codebar chapter and organise workshops in their city, and to support them throughout the process in any way we can. If this is something that you would like to do, we suggest that you first try and find a host for the first two workshops and sponsors that can provide you with food.
 
-- We will add your chapter to the codebar website and provide you with organiser access, a mailing list where people subscribed to your city can reach out to you and more information on how to use the app to announce and invite people to workshops.
+- We will add your chapter to the codebar website and provide you with organiser access, a mailing list where people subscribed to your city can reach out to you and more information on how to use the website to announce and invite people to workshops.
 
 - We will also set up any social media accounts you'd like, which you can use to promote your chapter and workshops.
 
 We can also help with:
 
-- promoting your chapter through our Twitter account [@codebar](https://twitter.com/codebar) with 9600+ followers and growing
+- promoting your chapter through our newslettert with over 12000+ subscribers and growing
 
 - reaching out to potential venues, sponsors and coaches in your city
 

diff --git a/_posts/2015-03-26-host-guide.md b/_posts/2015-03-26-host-guide.md
@@ -1,6 +1,7 @@
 ---
 layout: post
 title: "Host Guide"
+weight: 90
 ---
 
 ### Running a codebar workshop

diff --git a/_posts/2015-05-05-brandbook.md b/_posts/2015-05-05-brandbook.md
@@ -1,6 +1,7 @@
 ---
 layout: post
 title:  "Brandbook"
+weight: 20
 ---
 
 Welcome! This one page document is a short introduction to the codebar brand. It is very much work in progress and is meant to give you a high level overview about the Dos and Donts of the codebar brand.
@@ -9,6 +10,11 @@ Welcome! This one page document is a short introduction to the codebar brand. It
 
 All of our assets can be downloaded from our [assets GitHub repository](https://github.com/codebar/assets).
 
+You can also have access to our [brand kit on Canva
+](https://www.canva.com/brand/kAD9lbXPkEg)
+
+We recommend creating assets on Canva. We have templates, logos, icons and can help you with edits if you get stuck.
+
 ### Logo
 
 Our logo, mark and wordmark comes in two colour ways. Additionally, our logo comes in vertical and horizontal versions.

diff --git a/_posts/2025-12-17-chapter-organisers-monthly-meeting.md b/_posts/2025-12-17-chapter-organisers-monthly-meeting.md
@@ -0,0 +1,26 @@
+---
+layout: post
+title:  "Chapter Organiser Meetings"
+weight: 40
+---
+
+Currently, we hold a monthly chapter organiser meeting on the last Thursday of the month. These meetings are optional, but they’re a great chance to:
+
+- Meet other organisers across different chapters (especially helpful if you’re new)
+- Share what’s working and swap practical tips (venues, comms, formats, tooling, etc.)
+- Raise issues or blockers you’re having, and get support from other organisers and codebar HQ
+- Hear updates about what’s coming up across codebar (process changes, new resources, upcoming initiatives)
+- Align on next steps and leave with clear actions (if anything needs following up)
+
+## How to bring something to the meeting
+
+- If you have a topic/question, add it ahead of time (via the meeting issues list) so it can be included on the agenda.
+- Before the meeting, take a look at the open topics and upvote the ones you’d like discussed — we’ll prioritise the most upvoted items.
+
+## During and after
+
+- Join via the meeting link shared in the calendar invite or in the `#organisers` Slack channel. (Please make sure you are receiving these calendar invites. If not, speak to Charlene Kuye.)
+- After the meeting, notes will be added to the relevant GitHub issues, and if needed, action items will be assigned and followed up in the next meeting.
+- Read.ai summary notes will be checked and shared in the Slack channel after every meeting.
+
+**Note:** Sometimes just one person (or a representative) from each chapter will attend, but everyone is welcome. If you can’t make a meeting but still want to discuss chapter-related issues, reach out to Charlene on Slack.
diff --git a/_posts/2025-12-17-creating-a-workshop.md b/_posts/2025-12-17-creating-a-workshop.md
@@ -0,0 +1,104 @@
+---
+layout: post
+title: "Creating a workshop"
+weight: 60
+---
+
+This guide covers how to use the admin area of the codebar website if you are a chapter organiser, with a focus on creating a workshop.
+
+> **Screenshots:** The original doc includes screenshots. Add them as normal image files in the repo (recommended) and link them here, rather than pasting base64 images into the Markdown.
+
+## Intro
+
+Once you’ve been given admin access on the codebar website you’ll see extra options in the left-hand menu, including the ability to create sponsors, create workshops, view feedback, and access your chapter admin area under **My Chapters**.
+
+[comment]: <> (![Screenshot: admin menu](TODO-add-screenshot))
+
+## Chapter admin area
+
+In your chapter admin area you can see upcoming workshops, view students/coaches, and see the latest subscribers.
+
+[comment]: <> (![Screenshot: chapter admin area](TODO-add-screenshot))
+
+1. **Organisers list** for your chapter
+2. **Coaches and students** subscribed to your chapter  
+   - Clicking **Students** or **Coaches** shows a full list  
+   - Clicking **View students emails** / **View coaches emails** shows email addresses
+3. **View all workshops** shows every workshop your chapter has run (and lets you open old workshop admin pages)
+4. **Workshops list** shows the workshops you’ve created; click one to open its admin page
+5. **Latest subscribers** shows recent signups (name, pronouns, whether student/coach, and time). Clicking a person opens their member admin area.
+
+## Adding a sponsor
+
+If the company has **never hosted a codebar workshop before**, you’ll need to add them as a sponsor before creating the workshop. If they’re already in the system, you can skip to creating the workshop.
+
+- Go to the **New sponsor** tab in the left menu
+- Fill out the required fields and click **Create sponsor**
+
+Notes:
+- **Website:** usually the company website, unless they ask you to link elsewhere
+- **Avatar:** ask for a transparent-background PNG logo
+- **Address:** you don’t need latitude/longitude unless the map pin is wrong; **Directions** are useful if the location is hard to find
+- **Accessibility:** even if optional, do your best to add it (at minimum: step-free access to the workshop and bathrooms)
+- **Contact details:** the dropdown is useful if the person already has an account; otherwise add name/email manually
+
+[comment]: <> (![Screenshot: new sponsor form](TODO-add-screenshot))
+
+## Creating a workshop
+
+If it’s a new sponsor, make sure you’ve created the sponsor first.  
+If you need to change student/coach numbers for the host, go to https://codebar.io/admin/sponsors, find the sponsor, and edit it.
+
+- Go to the **Admin** tab and select **New Workshop**
+
+There are two parts depending on whether the workshop is **in-person** or **virtual**. For both, these fields are required:
+
+- Select your **chapter**
+- Select the **date**
+- Select the **start time** (include the 30 minutes of socialising beforehand)
+
+### In person (left side)
+
+- Select the **host**
+- Select your **sponsor(s)**  
+  (sometimes a different company sponsors food/drink; if it’s the same, select the same company as host)
+- Optionally set the date/time the workshop should **auto open RSVP**
+- Ensure **Invitable** is **unchecked** if you don’t want RSVPs yet (leave it checked if you do)
+- Click **Save**
+
+### Virtual (mostly right side)
+
+- Check **Virtual workshop**
+- Create a workshop channel in Slack and enter the **channel name**
+- Get the Slack channel URL (in Slack: click the channel name → Copy Link) and paste it in
+- Enter **coach** and **student** spaces
+
+> Note: we normally do not have a sponsor for virtual workshops, so don’t add one unless there is an explicit agreement.
+
+If you want people to RSVP right away, check **Invitable**. If you only want to list it for now, leave **Invitable** unchecked.
+
+[comment]: <> (![Screenshot: new workshop form](TODO-add-screenshot))
+
+## Workshop admin area
+
+Once your workshop is created you can edit it any time. Each workshop has its own admin page where you manage the workshop and attendees.
+
+[comment]: <> (![Screenshot: workshop admin page](TODO-add-screenshot))
+
+### Buttons at the top
+
+- **Edit** — edit workshop details
+- **Invite** — invite chapter members (usually choose **Everybody**)
+- **Labels** — download a CSV of attendees (useful if the host asks for a list)
+- **Attendees** — see attendees and what students are working on
+- **Emails** — view attendee emails (if you mass email, **BCC everyone**)
+- **Destroy** — you can destroy a workshop up to 3 hours after creating it
+
+Below the buttons you’ll see the venue, date, address, organisers, and student/coach spots.
+
+## Attendee list
+
+[comment]: <> (![Screenshot: attendee list](TODO-add-screenshot))
+
+1. Shows how many invitations were sent, RSVP counts, and waitlist counts (students/coaches).
+2.
diff --git a/_posts/2025-12-17-main-contacts-who-to-go-to.md b/_posts/2025-12-17-main-contacts-who-to-go-to.md
@@ -0,0 +1,35 @@
+---
+layout: post
+title:  "Main Contacts"
+weight: 110
+---
+
+## Charlene Kuye (Volunteer Coordinator)
+Email: charlene@codebar.io
+
+Go to Charlene for anything related to the smooth running of your chapter, including:
+
+- Support for chapter organisers (day-to-day operations and guidance)
+- Onboarding and off-boarding organisers
+- Help with 1Password and other login/access issues
+- Ordering stationery and chapter supplies
+- Support for coaches (new and existing), including ensuring they have the training and support they need to coach confidently
+
+## Arora Ashani (Community Manager)
+Email: arora@codebar.io
+
+Go to Arora for anything related to community growth and events, including:
+
+- Running events and workshops
+- Support with growing your chapter community
+- Increasing and supporting student numbers
+
+## Kimberley Cook (codebar Director)
+Email: kimberley@codebar.io
+
+Go to Kim for organisation-wide leadership, governance, and strategic support, including:
+
+- Escalations or sensitive issues that need director support
+- Partnerships, sponsorship, and high-level external relationships
+- Organisational strategy, priorities, and major decisions
+- Guidance on policies, safeguarding, or risk-related concerns