How to write a blog post for EU Code Week

Publication date: October 20, 2020

Blogging about your coding events gives you visibility among the Code Week community and can inspire other organisers to follow your approach. You can also use the blog post as a reference for your future activities.

Code Week blog posts should be light, short, written in simple language, short phrases and accompanied by many pictures or videos. For inspiration, have a look at the currently published blog posts.

What to write

In your blog post, you should answer these simple questions:

• What happened during the event?
• What was the event about?
• Where and when did it take place?
• Who participated?
• What were the most outstanding achievements/activities?
• How can readers replicate your approach or get inspired?

For each blog post, please send us 3-10 pictures. A YouTube video can also be embedded.

Don’t forget to choose an attractive title for your blog post. Also clearly mention who the author is and where they come from.

Tell a story and think about a bigger picture. Imagine you are an external reader who roughly knows what coding is but has never heard about your school, club or initiative. Explain how the event went, try to describe the atmosphere. Tell a story about 1 or several participants, share their emotions, what they thought/said at the end of the event.

You can also share practical details about the organisation of your event. Many other event organisers will read your blog post, and they will appreciate if you share your experience, if you tell them what worked well and what didn’t work.

Divide your text into short paragraphs. Remember: 1 paragraph = 1 idea.

Don’t forget to add hyperlinks in your text.

When to write

Ideally, you write your text within the week after your event. Your memories are fresh, and you will be able to tell the story with the main highlights; If you wait longer the emotions from the event go away, and you may also more easily forget substantial details

What to avoid

• Long phrases, long paragraphs
• Passive voice
  • “Participants were given presents” – not correct
  • “Participants received presents” or “We gave presents to the participants” – correct
• Repeating the same words
• Too narrow details
• Too many technical expressions

When you have your text and pictures ready, send it to info@codeweek.eu. The team will read your text and either come back to you with questions and comments or if the text is perfect, they will publish it on the Code Week blog.