How to Write a Hackathon Recap That Gets Published
A good recap helps people who were not there understand what happened, and helps people who were there remember it. Here is a structure that works.
Start with the facts
Open with what the event was, where and when it took place, and how many people took part. Readers should know the basics before the second paragraph.
Tell the story of one or two projects
Do not try to cover every team. Pick the winning project and one surprising one. For each, explain the problem, the approach and what the team learned.
Include the details people search for
- Event name and organizer
- City or online platform
- Dates and time zone
- Winners and prizes
- Links to the demo, the repository and the event page
Send good images
- Landscape photos or screenshots, at least 1600 pixels wide
- A short description for each image
- Only images you have the right to share
Keep it short
Between 400 and 900 words is plenty. Use headings, short paragraphs and a table if you are listing results.
Ready to send yours? Use the submission page and we will take it from there.