Everything your code club needs, on one website.

What a code club website needs

Parents and schools usually find a code club by searching for something local for a child who likes computers, so they want age range, venue and whether it is free before anything else. Volunteers and venues, such as libraries and schools, also look you up to see whether you are a safe, organised group.

What to publish

• Age range, session day and time, and the exact room or venue, with a note on parking or drop-off.
• What children actually build, for example Scratch games, web pages or Python, and what level they need to start.
• Whether children bring their own laptop or you provide equipment.
• How a parent books a place or joins the waiting list, and the term dates.
• Who the volunteers are, the safeguarding contact and how volunteers are checked.
• A showcase of finished projects, with permission from parents before any child's work or photo goes up.

Common mistakes to avoid

• Listing only a first name and a photo of a child's screen with no consent wording, which worries parents and breaches your own safeguarding approach.
• Never saying how a waiting list works, so families assume you are full and give up.
• Describing sessions in jargon like "computational thinking" instead of saying what a seven-year-old will make.

Frequently asked questions