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 well-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.
Until now, our articles have exclusively been written by LogRocket engineers and product managers. But in order to share a wider range of technical topics and opinions, we’re opening up our blog to the community. Starting today, we’ll be accepting contributions from community members, and offering competitive compensation for quality work.
What are we looking for?
We’re looking for passionate developers and technical writers who love writing informative and educational content. Some sample topics you could write about include:
- Frontend development best practices
- Product/UI/UX design
Here are some examples of the types of posts we like:
- Recreating the Chrome Console in React
- Make React Fast Again [Part 1]: Performance Timeline
- Visualizing Backend Performance in the Chrome DevTools
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, Facebook, etc.
- You can reach a wider audience. We regularly receive around 1 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.
Want to get started?
Email firstname.lastname@example.org with your name, a brief bio, and a link to a writing sample that showcases your technical writing ability. Do not send attachments. If you already have a post in mind, you can include that as well.