Do you love writing about frontend development? Want to get paid and have us promote your content to a wide audience? Read on for the details.
The LogRocket Blog is one of the most respected resources on the web for frontend devs. We take pride in publishing deep, technical content that helps developers do their jobs and stay up to date on new technologies.
LogRocket’s posts are by the community, for the community. We’re always looking to work with passionate developers and technical authors who love writing interesting and educational content.
Why you should write for LogRocket
- We’ll compensate you for your time. Depending on the scope and quality of each post, we’ll offer up to $350.
- We’ll do the work to promote your content across the web. Hacker News, Reddit, Twitter, LinkedIn, etc.
- You can reach a wider audience. We regularly receive around 3 million monthly views from readers all over the world.
- You get to help other developers. Help give back to the community by sharing your knowledge and unique perspective.
- You can still publish your piece on your own blog. We simply ask to keep it exclusive to us for the first month. Then you can publish it on your own self-hosted blog or portfolio.
What makes a great post for LogRocket
This is the question we’re asked most often. Some sample topics you could write about include:
- Tutorials on React, Redux, Node.js, Wasm, GraphQL, Rust, Flutter, etc.
- Frontend development best practices
- Product/UI/UX design
Here are some examples of the types of posts we like:
- React Table: A complete tutorial with examples
- Things you can’t do in Rust (and what to do instead)
- 7 most common web design mistakes according to psychology
As you think about your first (or your next) LogRocket post, consider the following questions:
1. Who is this post for?
The LogRocket Blog is for professional developers, so we assume our readers have some basic knowledge of web technologies. They aren’t students or beginners, but they may be junior-level. How can you help them to become better developers?
2. What makes your post unique?
Are there a lot of resources out there on the topic? Is it well covered in the docs? If we cover a beginner-level topic, we want our post to be the best resource out there. So what are those other resources missing?
3. Are you speaking from experience?
Have you struggled with the topic in the past? What unique perspective can you bring to solving the problem? What information do you wish you had found when you were googling the topic?
4. Are there alternative approaches to solving the problem?
Why choose this one? Is there an opportunity to compare/contrast two options? Is one option better for performance, UX, DX, etc.?
5. Does this topic have a useful professional application, or is it just cool/fun?
What are the use cases? How could it improve someone’s website, app, code in general?
6. Would you click on your article if it showed up in search?
What would someone google to find your article? Is the title clear, descriptive, and clickworthy?
7. Ultimately, what will the final draft look like?
Share a bulleted outline of the points you plan to cover. Think of it like a table of contents; your major bullet points should reflect your subheads. You want your post to be scannable so readers can easily find what they’re looking for.