diff --git a/_includes/sidebar.html b/_includes/sidebar.html
index 249c2d3..314358c 100644
--- a/_includes/sidebar.html
+++ b/_includes/sidebar.html
@@ -1,10 +1,11 @@
\ No newline at end of file
diff --git a/_posts/2014-12-12-mailing-list-policy.md b/_posts/2014-12-12-mailing-list-policy.md
deleted file mode 100644
index 680aade..0000000
--- a/_posts/2014-12-12-mailing-list-policy.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-layout: post
-title: "Mailing List Policy"
----
-
-codebar is a charity dedicated to promoting diversity in the technology development industry. We encourage active involvement in the tech community and are keen to communicate information to our students that would benefit their education.
-
-We have a dedicated mailing list for our community, as well as regular emails inviting them to upcoming events. If you would like to offer us something we would love to hear from you, but ask that you adhere to the following principles:
-
-- **No paid courses**. We spend a lot of our time trying to create opportunities and run free events. If you would like to run a free version of your course for us or offer free spots to an event you are running, we would love to hear from you.
-
-- Any offers/courses sent must be aimed at beginner to intermediate level developers and should specify the prerequisites and background knowledge required in order to attend - we welcome free conference tickets too!
-
-- All communication that you want us to forward to the codebar mailing list must align with the codebar [Code of Conduct](https://codebar.io/code-of-conduct).
-
-- No abusive, exclusionary or discriminatory language.
-
-- Any messages that deviate from this policy may be accepted at the sole discretion of the codebar organisers.
diff --git a/_posts/2014-12-19-becoming-a-sponsor.md b/_posts/2014-12-19-becoming-a-sponsor.md
deleted file mode 100644
index ce06886..0000000
--- a/_posts/2014-12-19-becoming-a-sponsor.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-layout: post
-title: "Sponsoring"
----
-
-### About codebar
-
-codebar is a charity that has been running free weekly coding workshops since October 2013, with London as its first chapter. Since then we have expanded to running workshops in 37 locations around the world - from Brighton, Manchester, Edinburgh, New York City, Berlin and Sydney, and the list goes on.
-
-We have coached over 14,000 students, with new people attending our events every week. Because of this our developer base has grown rapidly in a short period of time, but it has also substantially increased demand for space, coaches and resources. This in turn requires a substantial expansion in sponsorship investment so that we can not just run workshops, but also be able to provide help and support to our smaller chapters.
-
-All of codebar’s events are run on a volunteer basis, with every subject expert and coach giving their time for free.
-
-### Why should you sponsor?
-
-As a codebar sponsor, you will be part of the vibrant community facilitating the growth of a diverse community. We have a strict yet simple [code of conduct](https://codebar.io/code-of-conduct) that includes more detailed information.
-
-You will be helping to promote diversity within the tech sector and be part of an exciting community committed to narrowing the skills gap. Not only that, but you will also be contributing to the growth of much-needed technical skills and giving a further boost to the post-recession economy.
-
-Your sponsorship will enable more women, non-binary, LGBTQ+ and ethnic minorities to get started in development, or raise their skills to the next level. You will also have contact with developers of all levels at our workshops. Many of codebar’s students have found jobs as a direct result of the time they have invested to learn and develop their coding skills with us.
-
-Whatever investment you choose, your logo will appear on the codebar website along with a link to your site. You are also welcome to give a 5 minute talk at the beginning of an evening workshop you host on a topic you think our students will find interesting and informative.
-
-
-### How can you sponsor?
-
-There are different ways that you can help and support our vibrant and growing community. You can be a regular workshop supporter and offer your venue and food to a substantial amount of workshops taking place in your area.
-
-We also welcome monetary sponsorship to help us cover other expenses. The best way to make a monetary contribution is to use our online [donation portal](https://codebar.enthuse.com/donate/#!/).
-
-You can also come on board as a codebar partner for a 12 month partnership. If you're interested in this option, please drop us an email .
-
-
-### Why sponsor us
-
-Women in the UK make up 46% of the workforce but in technology the number drops to less than 20%. Stereotypes, socio-psychological factors, external barriers such as male-dominated environments and a lack of role models in the sector are some of the contributing factors.
-
-Supporting us means you provide women, non-binary, LGBTQ+, and ethnic minorities the tools to get started with their development career and further current skills.
-
-Sponsoring us is also a great way to attract fresh and passionate talent to your company and to show your active efforts in tackling the industry’s diversity problem.
-
-
-#### What your sponsorship money is being used for
-
-- Our infrastructure costs (we pay for all the services we use to manage both technical and administrative aspects of codebar from hosting, to accounting etc)
-- Promotional materials to help get the word out
-- Support for chapters that are at times unable to find local sponsorship for their workshops
-- Running more specialised events (all our events are free and run by volunteers - but we still need to handle food catering, marketing, planning and other administrative costs)
-- Travel cost reimbursement for students attending our workshops
-
-### What do you get in return?
-
-Whatever your investment, you can be proud knowing that you are an active member of this flourishing sector, enabling people to find jobs, enhance their existing careers and substantially improve the quality of life of those who are often discriminated against.
-
-Depending on your level of sponsorship, we will also list your logo and link on our website, thank you on all our socials, mention you in our bi-monthly newsletter and you will be welcome to distribute your marketing collateral at our events.
-
-We look forward to welcoming you to our evolving community!
diff --git a/_posts/2015-01-31-coordinator-guide.md b/_posts/2015-01-31-coordinator-guide.md
index a7c95ab..928bcdd 100644
--- 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. ).
+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. ).
12. Encourage them to come to the social gathering afterwards, which is a great way to meet new people. They should come.
@@ -50,7 +51,7 @@ 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.
@@ -58,6 +59,6 @@ codebar workshops are a team effort and we really appreciate you wanting to help
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
index 65f2fd3..6a7b2c5 100644
--- 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 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 we'll be able to find something :)
diff --git a/_posts/2015-02-05-organiser-guide.md b/_posts/2015-02-05-organiser-guide.md
index c42d2dd..20ea957 100644
--- a/_posts/2015-02-05-organiser-guide.md
+++ b/_posts/2015-02-05-organiser-guide.md
@@ -1,17 +1,18 @@
---
layout: post
title: "Organiser Guide"
+weight: 30
---
### Workshops
#### What do I need from a host?
-- **Space**. The requirements are different depending on the city. A workshop can be as small as 5-6 people or as big as 70 - or more if you have enough people helping out! Just make sure that the venue details are configured properly in the website before you send out any invitations.
+- **Space -** The requirements are different depending on the chapter. A workshop can be as small as 5-6 people or as big as 60 - or more if you have enough people helping out! Just make sure that the venue details are configured properly on the website before you send out invitations.
-- **Desks and chairs**. Make sure there are enough tables and chairs for everyone.
+- **Desks and chairs -** Make sure there are enough tables and chairs for everyone.
-- **WiFi and power**. The venue needs to have a fairly good and stable internet connection and enough power sockets for all the student laptops.
+- **WiFi and power -** The venue needs to have a good and stable internet connection and enough power sockets for all the student laptops.
- If it is possible please ask the host to label one of their toilets as gender neutral. We recommend using [this sign](https://www.refugerestrooms.org/rr-sign-no-handi.pdf).
@@ -19,37 +20,37 @@ title: "Organiser Guide"
- **Students and coaches**. We aim to have double the amount of students to coaches, and try to pair up 2 students who are working on the same tutorial with their assigned coach.
-- **Food and drinks**. Learning to code after a long day at work can be hard. Offering free food and giving people the opportunity to take a break and have something to eat before getting started makes our events more effective and accessible. You should also ask for vegetarian, vegan, and gluten-free options and also non-alcoholic drinks. The effort is minimal and then everyone can have something to eat. If you are stuck, ask us for suggestions!
+- **Food and drinks**. Learning to code after a long day at work can be hard. Offering free food and giving people the opportunity to take a break and have something to eat before getting started makes our workshops more effective and accessible. You should also ask for vegetarian, vegan, and gluten-free options and also non-alcoholic drinks. The effort is minimal and then everyone can have something to eat. If you are stuck, ask us for suggestions!
Not all companies are able to provide both space and food. If you need help finding a sponsor let us know.
#### Announcing workshops and sending out invitations
-You should aim to list your events at least a week before they take place to give people time to learn about and sign up to the event. Give a longer lead time for new chapters. When creating an event, you should make sure to not set it as `invitable` unless registrations are open.
+You should aim to list your workshops at least a week before they take place to give people time to learn about and sign up. Give a longer lead time for new chapters. When creating a workshop, you should make sure to not set it as `invitable` unless registrations are open.
-Anyone signed up to codebar will be able to RSVP to the event through the workshop page but only people subscribed to your chapter will receive an email invitation.
+Anyone signed up to codebar will be able to RSVP to the workshop through the workshop page but only people subscribed to your chapter will receive an email invitation.
-A few days out from the event, review the list of students for first-time attendees (anyone with a paw icon next to their name), and look for those with male pronouns or masculine-associated names. See if you can find their social media profile and check whether they meet the [eligibility criteria](https://codebar.io/student-guide#eligibility). If you're not able to find any information to indicate that they do meet the eligibility criteria, click the 'Eligibility' button on their profile to send out an automated eligibility check email. If they confirm that they're eligible, add a note to their profile so that you don't have to do this again. If they don't respond by midday on the day of the workshop, it's up to you whether you have a chat to them at the workshop or just remove them from the list.
+A few days out from the workshop, review the list of students for first-time attendees (anyone with a paw icon next to their name), and look for those with male pronouns or masculine-associated names. See if you can find their social media profile and check whether they meet the [eligibility criteria](https://codebar.io/student-guide#eligibility). If you're not able to find any information to indicate that they do meet the eligibility criteria, click the 'Eligibility' button on their profile to send out an automated eligibility check email. If they confirm that they're eligible, add a note to their profile so that you don't have to do this again. If they don't respond by midday on the day of the workshop, it's up to you whether you have a chat to them at the workshop or just remove them from the list.
#### Name badges
Giving people name badges helps out a lot. Remembering new names can be hard, especially for newcomers and this enables the attendees to always know who they are talking to and if they are a student or a coach, to avoid confusion.
-If the attendee list is long, you might want to have the labels printed instead. One of our sponsors has been kind enough to provide us with a free professional account at their label providing service and you can use to generate the addressing label template. You can to find the login in 1password.
+If the attendee list is long, you might want to have the labels printed instead. One of our sponsors has been kind enough to provide us with a free professional account with Big.first.name. You can to find the login details in 1password, and instructions on how use it [here](https://docs.google.com/document/d/1GTL2U-GbECjiIPJhryQTMsOrqDPfyTRsrMw1QLaWgVw/edit?usp=sharing).
-You will then have to get the list of the event attendees so you can import it and generate the template. You can do that by clicking *Export attendees* on the workshop's admin page. The list of attendees can also be retrieved by appending `.csv` to any invitation URL.
+If you're printing, you will have to get the list of the attendees so you can import it and generate the template. You can do that by clicking *Export attendees* on the workshop's admin page. The list of attendees can also be retrieved by appending `.csv` to any invitation URL.
If you don't have access to a printer at work, ask your host if they are able to handle printing the badges and supplying the labels. Alternatively, provide blank labels and sharpies so attendees can make their own badges.
You can also use different color stickers for the organisers and anyone helping out so that attendees know who to speak to if they need any help.
-### At the event
+### At the workshop
-As people arrive at the event check them in through the workshop admin page, and double check what tutorials the students have signed up for so that you can pair them up prior to the event. Also, make sure you give them their name tag. Doing all of this will enable you to track demand and enforce the codebar attendance policy. The coaches will also only start appearing in the [coach ranking](https://codebar.io/coaches) after their attendance is confirmed.
+As people arrive at the workshop check them in through the workshop admin page, and double check what tutorials the students have signed up for so that you can pair them up prior to the event. Also, make sure you give them their name tag. Doing all of this will enable you to track demand and enforce the codebar attendance policy. The coaches will also only start appearing in the [coach ranking](https://codebar.io/coaches) after their attendance is confirmed.
Make sure the WiFi details are displayed in prominent places.
-Depending on the size of the event we tend to spend the first half an hour having food and socialising before we pair people up around 19:00 (if we start at 18:30) and get started with coding. Some of our chapters run 5-minute lightning talks before they pair up the students and coaches. You are encouraged to try things out and see how it works better for you. Just remember to keep things running smoothly and allow the students at least 1:30 hour, if not more, of learning.
+Depending on the size of the workshop we tend to spend the first half an hour having food and socialising before we pair people up around 19:00 (if we start at 18:30) and get started with coding. Some of our chapters run 5-minute lightning talks before they pair up the students and coaches. You are encouraged to try things out and see how it works better for you. Just remember to keep things running smoothly and allow the students at least 1:30 hour, if not more, of learning.
Double check that the host has labelled one of their toilets as gender neutral. We recommend using [this sign](https://www.refugerestrooms.org/rr-sign-no-handi.pdf).
@@ -59,19 +60,19 @@ As you start pairing students and coaches, it is important to let the coach pick
If you have a lot of attendees, then you might need multiple organisers to help sign students in and note their planned topics of study. In these situations, a shared Google Doc can be useful to allow multiple contemporaneous editors. A common method is to list the students who've been signed in, in order of how difficult their subject is to find coaches to teach, from most difficult (e.g. advanced Java, PHP, iOS, testing, etc) to easiest (beginner HTML). You can then group students who are working on the same thing, and indicate a group by inserting line-breaks between groups.
-### After the event
+### After the workshop
-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.
+Encourage them to come to any social events following the workshop. Usually people don't get that much time to interact at the workshops 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
-Part of your job as organiser is to make sure that everyone feels welcome and comfortable. This might occasionally mean that you have to deal with small issues or potentially ban people from attending future codebar events.
+Part of your role as organiser is to make sure that everyone feels welcome and comfortable. This might occasionally mean that you have to deal with small issues or potentially ban people from attending future codebar events.
This is not something that anyone enjoys doing, however, our attendees are our priority and we need to make sure that codebar's [Code of Conduct](https://codebar.io/code-of-conduct) and [Eligibility Criteria](https://codebar.io/student-guide#eligibility) are enforced.
-If someone comes to you with a complaint, act on it promptly. If attendees are involved, speak to them in a private area where you cannot be overheard, or send them an email after the event. When passing on negative feedback about a coach, you may need to ask the student’s permission first, as this information can be identifying.
+If someone comes to you with a complaint, act on it promptly. If attendees are involved, speak to them in a private area where you cannot be overheard, or send them an email after the workshop. When passing on negative feedback about a coach, you may need to ask the student’s permission first, as this information can be identifying.
For difficult eligibility conversations, it often helps to remind people that our coaches, organisers and hosts donate their time and money to help those who have faced unfair barriers to entry into the tech world.
diff --git a/_posts/2015-02-06-bringing-codebar-to-your-area.md b/_posts/2015-02-06-bringing-codebar-to-your-area.md
index fa27fca..904968d 100644
--- 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.
+- 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 every 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 and drink.
-- 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 newsletter with over 12,000+ 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
index d50c9a5..fccd8a6 100644
--- 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
@@ -13,9 +14,9 @@ So you've decided to become a sponsor and host a codebar workshop? Awesome, than
- You’re welcome to invite up to five of your own guests to study at the workshop - just let us know who you’ll be bringing along.
-- To help us spread the word further, send us a transparent png version of your logo and we’ll set you up on the events page on our site.
+- To help us spread the word further, send us a transparent png version of your company logo and we’ll set you up on the workshop page on our website.
-- Find a food supplier for the event. It’s important to provide vegetarian, vegan and gluten-free options too. If you need help finding places to order from, get in touch with the codebar organiser(s) and they'll help you find a place.
+- Find a food supplier for the workshop. It’s important to provide vegetarian, vegan and gluten-free options too. If you need help finding places to order from, get in touch with the codebar organiser(s) and they'll help you find a place.
- As well as food, most of our hosts provides drinks too. Alcohol is not required. Please at least supply water.
@@ -45,4 +46,4 @@ So you've decided to become a sponsor and host a codebar workshop? Awesome, than
#### At the workshop
-One of the organisers will be at the venue around 6:00PM (30 minutes before official start time) to help you set up the space and check people in. Sessions usually last two and a half hours. Relax, have fun and enjoy your time as a codebar workshop host, and once again thank you very much.
+One of the organisers will be at the venue around 6:00PM (30 minutes before official start time) to help you set up the space and check people in. Workshops usually last two and a half hours. Relax, have fun and enjoy your time as a codebar workshop host, and once again thank you very much.
diff --git a/_posts/2015-05-05-brandbook.md b/_posts/2015-05-05-brandbook.md
index 6b9a313..f51351c 100644
--- a/_posts/2015-05-05-brandbook.md
+++ b/_posts/2015-05-05-brandbook.md
@@ -1,14 +1,20 @@
---
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.
+Welcome! This one page document is a short introduction to the codebar brand. It is very much a work in progress and is meant to give you a high level overview about the Dos and Donts of the codebar brand.
## Assets
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
new file mode 100644
index 0000000..e69874e
--- /dev/null
+++ 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](https://github.com/codebar/chapter-organiser-meetings/issues)) 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
new file mode 100644
index 0000000..15a062d
--- /dev/null
+++ b/_posts/2025-12-17-creating-a-workshop.md
@@ -0,0 +1,145 @@
+---
+layout: post
+title: "Website Guide (Chapter Organisers)"
+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.
+
+## 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**.
+
+
+
+## Chapter admin area
+
+In your chapter admin area you can see upcoming workshops, view students/coaches, and see the latest subscribers.
+
+
+
+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
+
+
+
+## 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.
+
+
+
+## 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.
+
+
+
+### 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
+
+
+
+1. Shows how many invitations were sent, RSVP counts, and waitlist counts (students/coaches).
+2. This drop down allows you to manually add someone (who has been email invited) from your chapter to the workshop if you need.
+3. On the left you have your list of students for the workshop and on the right you have your list of coaches.
+ - If you see a paw print next to someone's name it means this is their first time attending a codebar workshop.
+ - If you see a “!” sign, it means someone has RSVP’d and not shown up more than 2 times.
+ - If someone has added dietary requirements you will see this under their name
+ - The minus symbol next to someone's name means you can remove them from the workshops. Commonly used when someone emails beforehand saying they can no longer attend. This minus symbol changes at the start time of your workshop to a checkbox so you can check people in.
+ - Next to the students name you can see what they wish to work on during the workshop
+ - Each attendee is a hyperlink, which takes you to their member admin area.
+
+## Waitlist
+
+Once spaces are filled up, a waitlist will appear. As people drop out, the next person is automatically sent an email and offered a space.
+
+## Member admin area
+
+Every member of the codebar community has an admin area. You can view personal info, remove chapter subscriptions, see attendance history, send attendance/eligibility emails, leave notes, and ban members.
+
+### Actions
+
+- **Ban** — ban someone (e.g. bad attendance or code of conduct issues). You can choose the ban duration.
+- **Note** — add a note to someone’s profile (eligibility, behaviour, etc.).
+- **Eligibility** — send an eligibility email if you’re unsure whether a student is eligible.
+ _Note: a member who is only subscribed as a coach won’t have this button._
+- **Attendance** — send an attendance email if someone repeatedly RSVPs and doesn’t show up.
+
+### What you’ll see on the page
+
+1. Action buttons (Ban / Note / Eligibility / Attendance)
+2. Personal information
+3. Chapters the member subscribes to (remove a subscription using the **X** next to the chapter)
+4. RSVP vs attended counts (useful when deciding whether to send an attendance email)
+5. List of workshops/events they RSVP’d to:
+ - A **tick** indicates they attended
+ - A **!** indicates they RSVP’d but didn’t show up
+ - Monthlies attended may be listed underneath too
+
+## Updating sponsor information
+
+You can update sponsor information at any time. Specially useful if workshop numbers change, the company updates their logo or moves office. To do this :
+
+1. Go to https://codebar.io/admin/sponsors
+2. Find your sponsor and click **Edit**
+3. Make changes and click **Save**
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
new file mode 100644
index 0000000..37aac84
--- /dev/null
+++ 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
diff --git a/_posts/2025-12-17-photo-guide.md b/_posts/2025-12-17-photo-guide.md
new file mode 100644
index 0000000..9185809
--- /dev/null
+++ b/_posts/2025-12-17-photo-guide.md
@@ -0,0 +1,45 @@
+---
+layout: post
+title: "Photo Guide"
+weight: 70
+---
+
+Photos help us celebrate the community, thank the people who make workshops possible, and show future students what codebar feels like. Here’s how to do it well (and respectfully).
+
+## Before the workshop
+
+- **Add the host logo banner:** If the venue/host has provided a logo banner (physical or digital), set it up where it can appear in a few photos (or use it as a backdrop for a quick group shot).
+- **Seek permission first:** Make sure the host/venue is happy for photos to be taken in the space and shared publicly.
+- **Tell everyone upfront:** At the start of the workshop, let attendees know you’ll be taking photos and that anyone can opt out, no explanation needed.
+- **Create an opt-out option:** Offer a simple way to opt out (e.g., “Tell an organiser anytime”, or a sticker/badge/hand signal). If someone opts out, avoid photographing them and don’t post images where they’re identifiable.
+
+## During the workshop
+
+- **Focus on the atmosphere:** Aim for friendly, welcoming photos that show learning and collaboration.
+- **Get a mix of shots:**
+ - A wide shot of the room (from the back/side)
+ - Small groups pairing or coaching (over-the-shoulder works well)
+ - A “thank you” photo with the host logo banner visible
+ - Optional: a group photo at the end (only if people are comfortable)
+- **Avoid sensitive content:** Don’t capture laptop screens with personal data, email addresses, or private messages visible. Also watch what’s in the background—avoid photos that include confidential company information on walls, posters, screens, or whiteboards (e.g., internal plans, names, passwords, access codes, meeting notes, or diagrams).
+ When in doubt, check with the host or leave it out, and choose another photo.
+
+## Quick photography tips
+
+You don’t need expensive equipment to capture the fun and community spirit of a codebar workshop. Here are some tips:
+
+- Natural light is best (stand near windows if possible).
+- Take a few versions of each shot — people blink!
+- Keep it candid but considerate: Don’t interrupt learning; take photos quickly and move on.
+- Prioritise comfort: If someone looks uncomfortable, don’t take the photo.
+
+## After the workshop
+
+- **Share photos on Slack:** Post a small selection in the `#general` Slack channel, so the wider community can celebrate and see what other chapters are doing.
+- **Post to social media:**
+ - Share 3–8 of the best photos (quality over quantity).
+ - Tag the host/sponsor and coaches — it’s a great public way to say thank you.
+ - Keep captions positive and community-focused (e.g., what was learned, how it felt, gratitude to supporters).
+ - **Double-check opt-outs:** Before posting publicly, ensure no one who opted out is visible/identifiable.
+
+
diff --git a/_posts/2025-12-17-pre-post-workshop-lists b/_posts/2025-12-17-pre-post-workshop-lists
new file mode 100644
index 0000000..2615f5e
--- /dev/null
+++ b/_posts/2025-12-17-pre-post-workshop-lists
@@ -0,0 +1,59 @@
+---
+layout: post
+title: "Event Checklists"
+---
+
+## Pre Workshop Checklist Two+ weeks before the workshop
+
+- [ ] Confirm venue with host
+
+## One week before the workshop
+
+- [ ] Create the workshop on [codebar.io](http://codebar.io)
+- [ ] Make the workshop invitable
+- [ ] Send out invite emails
+- [ ] Advertise event link on
+ - [ ] Slack
+ - [ ] Social media (Linkedin/Instagram etc)
+ - [ ] Other channels (fliers, whatsapp groups, other communities)
+
+## The day before the workshop
+
+- [ ] Send the host the number of attendees and their names. Do not share attendee emails!
+- [ ] Post on social media and mention if spots are still available
+ - [ ] Slack
+ - [ ] Instagram
+ - [ ] Linkedin
+ - [ ] Other
+- [ ] Check all students and coaches are slack members.
+ - [ ] If not email your chapter email and bcc the attendees asking them to join with a link and instructions of what channel to join
+- [ ] (Optional) Send photos of the building and instructions to get in to attendees.
+
+## Day of the Workshop
+
+- [ ] Send the host number of attendees and their names,
+- [ ] Create Pairing Sheets
+- [ ] Print name badges
+
+# Running the workshop
+
+- [ ] Arrive 20 mins before the scheduled start time and meet the host
+- [ ] Check-in attendees on [codebar.io](http://codebar.io)
+- [ ] Keep an eye on Slack for people having issues finding the venue or getting in
+- [ ] Take pictures (see photo guide)
+
+# Post Workshop Checklist
+
+- [ ] Email the sponsor/host thanking them for hosting (see [template](https://docs.google.com/document/d/1862mTbiyEZsL0fxRzAHL9WBMsr66Mbxj-PD2qQ3O5Wg/edit?usp=sharing))
+ - [ ] Ask to schedule in the next workshop if applicable.
+- [ ] Post images on the Slack general channel
+- [ ] Post on social media
+ - [ ] Insta
+ - [ ] Tag host
+ - [ ] Linkedin
+ - [ ] Tag Host
+ - [ ] Tag mentors
+ - [ ] Attach pictures
+ - [ ] Other
+
+
\ No newline at end of file
diff --git a/_posts/2025-12-17-themed-events b/_posts/2025-12-17-themed-events
new file mode 100644
index 0000000..610bb76
--- /dev/null
+++ b/_posts/2025-12-17-themed-events
@@ -0,0 +1,34 @@
+---
+layout: post
+title: "List of themed events"
+---
+
+Here are suggestions for some one-off events you can run as a chapter
+
+Using AI workshop
+
+- Teach students how to effectively use AI in their coding workflows using industry standards.
+
+CV workshop
+
+- Run an event focused around interviewing and writing a CV, have attendees and coaches give each other CV reviews as part of it
+
+Christmas/holiday themed workshop
+
+- Christmas themed event
+
+Show and tell
+
+- Everyone presents a personal project they’re working on/made
+
+Non technical events
+
+- Games night
+- Social
+- Sticker exchange, where everyone brings in stickers and swaps them with one another
+- Picnic
+
+Uncodebar
+
+- A single day unconference. Speak to codebar HQ if you’d like to run one and we’ll support.
+
diff --git a/_posts/2025-12-17-website-guide-monthly-organisers.md b/_posts/2025-12-17-website-guide-monthly-organisers.md
new file mode 100644
index 0000000..fd1f354
--- /dev/null
+++ b/_posts/2025-12-17-website-guide-monthly-organisers.md
@@ -0,0 +1,111 @@
+---
+layout: post
+title: "Website Guide (Monthly Organisers)"
+weight: 50
+---
+
+### How to use the admin area of the codebar website (for monthly organisers)
+
+## Intro
+
+Now that you’ve been given admin access on the codebar website you’ll be able to see some extra options on the left side menu — mainly the ability to create new monthly events.
+
+
+
+
+## Creating a monthly event
+
+_If it’s a new sponsor, make sure that a sponsor has been created first. If you need to change the student/coach number for the workshop, visit https://codebar.io/admin/sponsors, find your sponsor and edit it._
+
+1. Go to the **Admin** tab in the top menu.
+2. Select **New Monthly**.
+3. Fill out the form:
+ - **Name:** e.g. _February Monthly_
+ - **Slug:** a unique slug, e.g. `monthly-feb-2020`
+ - **Date:** select the event date
+ - **Time:** normally **6:30PM** start
+ - **Description:** this is **Markdown**. It’s easiest to copy an older monthly description and update the details/speakers.
+ - **Space:** the number of people the host can accommodate
+ - **Venue:** select the host from the dropdown
+ - **Organisers:** add organisers for the event
+ - **Chapter:** select the chapter this monthly is for
+ - **Inviteable:** check/uncheck depending on whether the event is open for RSVP yet
+ (You may want to list the event but not open RSVP right away.)
+
+## Monthly admin area
+
+_Once your monthly event has been created you can edit it at any point._
+
+Each monthly event you create has its own admin page. It’s where you manage the event and attendees.
+
+
+
+### Top buttons
+
+- **Invite** — invite members of your chapter to the workshop. You can choose **Students**, **Coaches** or **Everybody** (usually **Everybody**).
+- **Edit** — edit event details.
+- **Emails** — view attendee emails. If you mass email, **make sure you BCC** everyone.
+- **Labels** — download a CSV of attendees (useful if a host asks for a list beforehand).
+
+You’ll also see key event info (venue, date, address, organisers, number of spaces), and the event description (often speaker info).
+
+### Attendee list
+
+
+
+- **a)** At the top you can see how many people have RSVP’d.
+- **b)** You may see a dropdown to manually add someone (who has been email-invited) from your chapter.
+- **c)** You’ll see the attendee list:
+ - The **minus** symbol next to someone’s name removes them from the event (commonly used when someone emails to cancel).
+ - At the start time of your workshop the minus symbol changes to a **checkbox** so you can check people in.
+ - Each attendee is a **link** to their member admin area.
+
+#### Waitlist
+
+Once spaces are filled up, a waitlist link appears. The waitlist is kept in Airtable. As people drop out, email someone from the waitlist to offer them a spot.
+
+## Member admin area
+
+Every member of the codebar community has an admin area. You can view personal info, remove chapter subscriptions, see attendance history, send attendance/eligibility emails, leave notes, and ban members.
+
+### Actions
+
+- **Ban** — ban someone (e.g. bad attendance or code of conduct issues). You can choose the ban duration.
+- **Note** — add a note to someone’s profile (eligibility, behaviour, etc.).
+- **Eligibility** — send an eligibility email if you’re unsure whether a student is eligible.
+ _Note: a member who is only subscribed as a coach won’t have this button._
+- **Attendance** — send an attendance email if someone repeatedly RSVPs and doesn’t show up.
+
+### What you’ll see on the page
+
+1. Action buttons (Ban / Note / Eligibility / Attendance)
+2. Personal information
+3. Chapters the member subscribes to (remove a subscription using the **X** next to the chapter)
+4. RSVP vs attended counts (useful when deciding whether to send an attendance email)
+5. List of workshops/events they RSVP’d to:
+ - A **tick** indicates they attended
+ - A **!** indicates they RSVP’d but didn’t show up
+ - Monthlies attended may be listed underneath too
+
+## Updating sponsor information
+
+You can update sponsor information at any time. Specially useful if workshop numbers change, the company updates their logo or moves office. To do this :
+
+1. Go to https://codebar.io/admin/sponsors
+2. Find your sponsor and click **Edit**
+3. Make changes and click **Save**
+
+## FAQ
+
+### I want to update some information about the host/sponsor?
+
+Edit it via https://codebar.io/admin/sponsors → **Edit**.
+You can change student/coach number, address, contact details, etc., then click **Save**.
+
+### What does it mean when a workshop is “invitable”?
+
+It means members of your chapter can RSVP to the event.
+
+### If I send out email invites again what will happen?
+
+Only people who subscribed since the last invite will receive it. It can be worth sending again if you know a bunch of people subscribed recently.
diff --git a/css/main.css b/css/main.css
index fda89a9..5c47138 100644
--- a/css/main.css
+++ b/css/main.css
@@ -143,3 +143,7 @@ tbody tr:hover td{
.color.magenta {
background: #ff036a;
}
+
+img {
+ width: 100%;
+}
diff --git a/images/codebar-logo-chapter-horizontal.png b/images/codebar-logo-chapter-horizontal.png
index 12569a2..fcc868d 100644
Binary files a/images/codebar-logo-chapter-horizontal.png and b/images/codebar-logo-chapter-horizontal.png differ
diff --git a/images/codebar-logo-horizontal.png b/images/codebar-logo-horizontal.png
index 2b4a2eb..90ad04c 100644
Binary files a/images/codebar-logo-horizontal.png and b/images/codebar-logo-horizontal.png differ
diff --git a/images/codebar-logo-restricted.png b/images/codebar-logo-restricted.png
index 0e59a5b..168323b 100644
Binary files a/images/codebar-logo-restricted.png and b/images/codebar-logo-restricted.png differ
diff --git a/images/codebar-logo.png b/images/codebar-logo.png
index 40c8e6c..906fc56 100644
Binary files a/images/codebar-logo.png and b/images/codebar-logo.png differ
diff --git a/images/codebar-mark.png b/images/codebar-mark.png
index 4638818..4419771 100644
Binary files a/images/codebar-mark.png and b/images/codebar-mark.png differ
diff --git a/images/creating-a-monthly-assets/admin-navigation.png b/images/creating-a-monthly-assets/admin-navigation.png
new file mode 100644
index 0000000..f133f9c
Binary files /dev/null and b/images/creating-a-monthly-assets/admin-navigation.png differ
diff --git a/images/creating-a-monthly-assets/attendee-list.png b/images/creating-a-monthly-assets/attendee-list.png
new file mode 100644
index 0000000..302ac39
Binary files /dev/null and b/images/creating-a-monthly-assets/attendee-list.png differ
diff --git a/images/creating-a-monthly-assets/monthly-admin-area.png b/images/creating-a-monthly-assets/monthly-admin-area.png
new file mode 100644
index 0000000..b7fe341
Binary files /dev/null and b/images/creating-a-monthly-assets/monthly-admin-area.png differ
diff --git a/images/creating-a-workshop-assets/admin-navigation.png b/images/creating-a-workshop-assets/admin-navigation.png
new file mode 100644
index 0000000..ab10004
Binary files /dev/null and b/images/creating-a-workshop-assets/admin-navigation.png differ
diff --git a/images/creating-a-workshop-assets/attendee-list.png b/images/creating-a-workshop-assets/attendee-list.png
new file mode 100644
index 0000000..f19742e
Binary files /dev/null and b/images/creating-a-workshop-assets/attendee-list.png differ
diff --git a/images/creating-a-workshop-assets/chapter-admin-area.png b/images/creating-a-workshop-assets/chapter-admin-area.png
new file mode 100644
index 0000000..9687d99
Binary files /dev/null and b/images/creating-a-workshop-assets/chapter-admin-area.png differ
diff --git a/images/creating-a-workshop-assets/new-sponsor.png b/images/creating-a-workshop-assets/new-sponsor.png
new file mode 100644
index 0000000..907f1bc
Binary files /dev/null and b/images/creating-a-workshop-assets/new-sponsor.png differ
diff --git a/images/creating-a-workshop-assets/new-workshop.png b/images/creating-a-workshop-assets/new-workshop.png
new file mode 100644
index 0000000..cd78d53
Binary files /dev/null and b/images/creating-a-workshop-assets/new-workshop.png differ
diff --git a/images/creating-a-workshop-assets/workshop-admin-page.png b/images/creating-a-workshop-assets/workshop-admin-page.png
new file mode 100644
index 0000000..397b275
Binary files /dev/null and b/images/creating-a-workshop-assets/workshop-admin-page.png differ
diff --git a/index.html b/index.html
index 1b27394..336d32e 100644
--- a/index.html
+++ b/index.html
@@ -5,7 +5,8 @@
- {% for post in site.posts %}
+ {% assign sorted_posts = site.posts | sort: "weight" %}
+ {% for post in sorted_posts %}