Write for Us
Since its humble beginnings in 1999, SitePoint was created to inform, inspire and engage the web community through informative content. We’ve amassed more than 10 million readers per month and produced more than 10,000 books and articles combined.
We always welcome having new writers join our contributor pool. They must have a strong desire to produce quality content with actionable advice that readers can apply in their own projects.
In return, we pay our writers above industry rates for their work.
What kind of content do we publish?
Each month, we produce a hub. We focus our energies on one topic, creating content across articles and books that provide readers with a linear path to competency in that skill. In recent months, we’ve created hubs covering React, web performance, and analytics.
In future months, we’ll be looking at subjects like Node, Angular, UX prototyping and Vue. We add to our list of planned hubs as each quarter progresses.
Generally, the content required for each hub is determined in advance by the hub editor, and assigned to available authors. We welcome ideas from authors as hubs enter their planning phase, but pitching specific article ideas no longer forms a core part of our editorial process.
Expressions of interest
Below you’ll find an embedded form you can use to tell us about yourself. If you’re a good fit, we’ll add you to our contributor pool. When editors begin planning upcoming hubs, they’ll put out a call for interest to the contributor pool, seeking authors with the relevant expertise.
Tell us a little about yourself and what you do, which technologies and web skillsets you have expertise in, and point us towards some of your existing written work.
Hubs require us to produce up to 40 pieces of content in a given month, all of them closely related and building on one another, with very little margin for these projects to go into overtime. As such, before you send us your expression of interest, we ask you to consider whether you’re willing to meet the demands of this kind of project. We’ll need you to:
- Be fully committed to completing any articles you agree to write
- Live and die by the mantra on time, every time
- Not simply care about hitting word count targets – you care deeply about ensuring your reader receives all the knowledge needed to effectively tackle real-world problems afterwards.
If you look like a good fit, we’ll be in touch with next steps. If the form does not display, you’ll also find it here.
Some of our editors will assess a writer’s skills, and help them develop further, by engaging them in our Peer Review program.
The goal of Peer Review is to ensure all of SitePoint’s articles are of the highest standards. It is also there to help authors with their writing through constructive feedback from the editor and fellow authors.
You can find more details about it here.
Note: All our Peer Review processes are completed via GitHub, therefore you must have a GitHub account to be involved.
Working with editors
Our editors at SitePoint are all professional developers, designers and web people at the top of their respective fields.
Most editors manage content production through Trello, a project management platform. This is where most of the communication between you and the editor will occur. Other editors use GitHub or email for private discussions. Your editor will instruct you on the best communications medium to use, and give you tips for getting the most out of them.
The editor is your primary contact during hub production, and works directly with you as your article is developed. They ensure that the published article is concise and correct, providing constructive feedback for you along the way.
Your relationship with the editor needs to be managed effectively. Here are some important things to bear in mind:
- Deadlines are important. If something is amiss and you are unable to meet the scheduled deadline, please inform the editor why as soon as possible. Generally they are very understanding.
- Proofread your article draft before submission. A clear structure will make the editorial process easier (and quicker) for the both of you. Usually the rule of thumb is:
- Paragraphs presenting an idea that supports your viewpoint
- Conclusion/Summary that reinforces what you’ve said
- Do not take feedback as a personal attack. Editors will always provide feedback that is constructive and aids the development of your article.
- One editor looks after many authors. They may be delayed in answering your enquiries. Be patient.
You can learn more about the process of working with editors in our GitHub Repo.
We take plagiarism very seriously at SitePoint. We use Plagiarisma to ensure all articles are original.
If you have blatantly plagiarized your article from another writer, we will find out. As consequence you will automatically be removed from the contributor pool, with your name blacklisted in our list of authors.
If you wish to cite another source to better explain your viewpoint, please properly credit them in the article by linking to the original source.
Contact SitePoint for permission
Authors may publish an excerpt of their article, along with a link to the full version, on their personal site providing they have received permission first. Request this permission by emailing your editor and explaining where (with a link) the excerpt will be published.
We do not permit non-authors to republish articles elsewhere, regardless of the amount of material they plan to republish.
Attribution (and att text)
You must include the following text at the beginning of your excerpt:
This post was originally published [link to full article on SitePoint].
Artwork and design
The design and artwork used in SitePoint articles is copyrighted and may not be republished.
We consider translation requests on a case-by-case basis. Email firstname.lastname@example.org to ask about translating a given article. In some cases we have existing arrangements with translation companies, so we will not be able to grant permission.
Sites offering translations to SitePoint content must be freely available, translate the work faithfully, and link to the original post:
This post has been translated. The English version was originally published [link to full article on SitePoint].
This documentation is for authors to refer to as they write their first article. It includes detailed, technical information about style guides, formats, code, accessibility and more.
You can access the documentation at our GitHub Repo.