Community/Guidelines
Community writing guidelines
RecallRun publishes articles from developers, engineers and tool builders. Anyone can read them without an account. To write one, sign in for free, follow these guidelines and submit your post for review.
What we publish
- Tech articles: tutorials, experiments, architecture write-ups, lessons from production, explainers on AI, data, software engineering, cloud, security and IT.
- Tools: a developer tool, library or product you built or use, explained in enough depth that readers learn something even if they never install it.
What makes a post good
- Specific and first-hand: real code, real numbers, real decisions and what you would do differently.
- Code you have run. Say which versions you used.
- At least 150 words; most good posts are 800 to 2,500.
- A clear title and a one- or two-sentence summary that says what the reader will get.
- Plain language. Explain acronyms the first time you use them.
Rules
- Your own work. Don't copy other people's text or images. Quote briefly and link the source. If you published the post elsewhere first, say so and link the original.
- Written for people. You may use tools to help you write, but you are responsible for every claim. Unchecked, generic or mass-generated text is rejected.
- Honest about tools. Tools posts must say how you are connected to the tool: you built it, you work for the company, you were paid or given access, or no connection. Pure adverts and affiliate-only posts are not accepted.
- Safe links only. Use full https links to the real destination. No link shorteners, no direct downloads of programs, no lookalike or unsafe sites.
- No secrets. Never include passwords, API keys, tokens or private keys, even fake-looking ones. If you post a risky command, warn readers clearly.
- Respect people. No harassment, hate, personal data about others, scams or instructions for causing harm.
How review works
- Automatic checks run the moment you submit: length and formatting rules, a scan for leaked keys and dangerous commands, a safety check on every link (redirects, lookalike domains, known malware and phishing lists) and an AI review of topic, quality, originality and safety.
- If something needs fixing, the post comes straight back to you with the reasons, so you can edit and resubmit.
- Posts that pass go to a RecallRun editor, who approves them, asks for changes or declines them with a note. Nothing is published without a person approving it.
- Published posts show your name and link to your author page. Links are re-checked every week; a post whose link becomes unsafe is taken down until it's fixed.
After publishing
- Updates: you can edit a published post at any time. Your changes go through the same checks and review, and readers keep seeing the current version until the update is approved.
- Notifications: you hear about every review result, publication, feature and view milestone in your notifications inbox, and by email if you switch it on in account settings.
- Stats: your writer dashboard shows views per day and the countries your readers come from.
- Taking it down: you can take a post down whenever you like; it goes back to your drafts.
Rights
You keep the copyright to your post. By submitting it you confirm you have the right to publish it, and you give RecallRun a non-exclusive, worldwide licence to publish, display and promote it (for example, sharing it on our social accounts with your name). Editors may fix typos and formatting. You can take a published post down at any time from your writer dashboard. Full details are in the terms and privacy policy.