Contact STR Coding Club

There is one way to contact STR Coding Club and this page explains it. Corrections to our first steps in coding, Python practice, club projects and teaching code coverage, questions, and commercial proposals all go to the same place, and below is how to write so that yours gets answered quickly.

The inbox

[email protected]

That mailbox goes to the editor's desk. It is the same address whether you are flagging a typo or floating a business idea.

Commercial enquiries

Proposals go to the one inbox like everything else. We take on very few, and we say no to most, so check the editorial policy before investing effort in a pitch.

How quickly we answer

Answers come by email, generally within two working days, and only by email. The missing phone line is a choice, not a gap we forgot to fill.

Mistakes

Complaints about accuracy get priority over everything else in the inbox. Be specific rather than gentle. The rules we follow when fixing something are in the editorial policy.

Beyond what we can do

We cannot recover an account for you, act as a go between with a third party service, or give advice tailored to your personal circumstances. STR Coding Club publishes general information about first steps in coding, Python practice, club projects and teaching code, and the legal notice explains where that line sits.

What to include

A precise message earns a precise reply, often the same day. A vague one waits while we write back to ask what you meant.

• Lead with the question. Context is useful, but not first.
• Paste the address of the page you are writing about, and the sentence that prompted the message.
• If a page looks broken, say which browser and which device, and send a screenshot if you can.

Who reads this

Whoever picks up your message has their name on articles here. We keep it that way so nobody can hide behind a shared support identity.