webrtcHacks is a blog focused on the WebRTC developer community. The majority of our content is written by guest authors – these are generally known experts who want to share their learnings and experiences. Our posts are written by engineers and developers for a technical audience. Chad typically spends several hours working with the author and editing over a couple iterations before we publish. Fippo provides additional technical review.
What content do we accept?
Our posts usually fall into one of the following categories:
- Code walk-throughs of open source RTC projects
- Architectural guides that provide general value
- Reverse engineering of popular RTC services
- Analysis or technical trends within the developer community
- Creative ways to (ab)use the WebRTC API
The content should be unique and valuable to RTC developers. It can be geared at developers just getting started with WebRTC, made for the deep experts in the community, or for levels in-between.
What we don’t accept
We never accept posts that are:
- Commercial in nature
- Require purchase to be of value
- Solely setup to optimize for someone’s SEO
- Reposts that have already been placed elsewhere or will be placed elsewhere
If you are not a webrtcHacks reader then you most likely will not be a good webrtcHacks guest author.
If we agree with you on a topic, we will work with you to make it great. Below are some guidelines for writing:
- We are flexible in the tool you write with. webrtcHacks.com is hosted on WordPress. I can get you a guest author login, but usually start something like Google Docs to make collaboration and edits easier (I use wordable.io to transfer Google Docs into WordPress)
- We usually recommend sharing an outline before you dig too deep into writing
- We do not have strict length guidelines, but most of our posts tend to be thousands of words – we like difficult topics and covering them thoroughly typically requires some length
- Make sure to link to relevant reference materials and original sources you site
- Add diagrams, code examples, and/or graphics whenever they make sense. We generally like to put some kind of visual every 500 to 1000 words to break up the text.
- Don’t be commercial – as a guideline, we let you make one reference to company you work for and we will reference it in our intro
- Fippo will provide a technical review and Chad will help edit
Read our articles to get some ideas.
Would you like to contribute?
Send an email to chad AT webrtchacks.com or message him on twitter with your idea.