What we publish
We look for articles that make front-end development genuinely easier to understand. The bar is simple: a reader should finish your article able to do something they could not do before, ideally by pasting your example straight into the editor.
- Beginner-friendly tutorials for HTML, CSS and JavaScript
- Productivity deep-dives: editor workflows, Emmet, debugging habits, keyboard-first editing
- Explainers that untangle confusing concepts: color systems, layout, the DOM, events
- Honest tool comparisons and workflow write-ups from real projects
- Case studies: how you fixed a specific bug or built something small and interesting
The rules (please read before pitching)
These keep the blog useful for readers and fair for writers:
- Original content only — we check every submission against plagiarism and AI-text detectors; republished or spun articles are rejected
- 800+ words with at least one runnable code example the reader can try in a live editor
- Clear, human voice — explain like a helpful senior colleague, not a documentation dump
- Correct and current — test your code before submitting and keep syntax up to date
- One or two relevant links maximum inside the body (to your own useful resource or a canonical reference); the author bio may include one profile link
- No gambling, crypto hype, essay mills, adult content or thin 'SEO articles' — these waste everyone's time
What you get
Every accepted article is published with a full author byline and short bio, which means a real byline credit on a growing developer blog with a dofollow link to your profile or site. You keep the right to republish elsewhere after 30 days with a canonical note. As the site's readership grows, accepted authors are first in line for paid writing commissions and long-term contributor spots.
We edit lightly for clarity and consistency — you always see and approve the final version before it goes live.
How to pitch
Send an email to [email protected] with "Guest post pitch" in the subject line. Include: the working title, a three-sentence summary, an outline of the main sections, links to two writing samples (published anywhere — a blog, GitHub README, Dev.to post all count), and the author name plus short bio you want published.
We reply to every serious pitch within a few business days — usually with a go-ahead, a suggestion to angle it differently, or an honest no. Accepted drafts are typically published within two weeks of final edits.