Engagement/Developer Engagement/Hacks blog
What Mozilla Hacks is - our vision
Mozilla Hacks is one of Mozilla's most important channels for developer outreach and engagement. We want it to be one of the key resources for people developing for the Open Web, talking about both news and in-depth descriptions of technologies and features. We will cover both development tips and tricks in general, but also look at features in Mozilla's products from a technical perspective - to show our approach and line of thinking, and hopefully inspire other companies to implement what we have.
Mozilla Hacks is, just like MDN (Mozilla Developer Network), a web browser agnostic resource, focused on the Open Web and sharing knowledge with all web developers out there.
Mozilla Hacks is not a press release channel and we don't reblog existing blog posts. We aim to have original content. If we find an interesting blog post, we might highlight it, but always with our own take.
Our goal is also to make as much information as possible about the blog publicly available, such as number of readers, most popular posts and more.
Mozilla Hacks aims to be one of the key web sites people will turn to for unbiased and expert knowledge about developing. Our intent is to have at least three descriptive articles per week, explaining a feature or technology.
Members of the Developer Engagement Team are writing for Mozilla Hacks, but any other Mozillian is also welcome to contribute! If you know something interesting that would be great to share with the readers of Mozilla Hacks, please let us know! We can be reached at mozhacks [at] mozilla [dot] com. When it comes to personal branding, we hope that the exposure you will get - both as an author and in the Mozilla context - will be good motivation for deciding to write for Mozilla Hacks! And if you have the technical expertise, but aren't sure about the writing, we'd be more than happy to help put together an article together with you.
We prefer original content, not reblogged, and if you want to blog in your own blog we would really like to see different versions/takes on the content. Additionally, we want to release things in Mozilla Hacks the same time as your possible personal blog post - otherwise, it's already on Twitter, Planet Mozilla and more, and some of the "oomph" factor and possibilities are missed.
We would also like to feature guest posts from prominent people within the web business. There are so many talented people out there, and we would love to highlight and share your knowledge!
We can't stress enough that Mozilla Hacks is not a billboard or announcement channel. It is there for us to have a dialog with developers out there, to hear their opinions, give them clarifications and for them to voice their takes on what we say. A blog post author is responsible for moderating and replying to comments. Not every comment needs a reply, but questions and similar should be addressed. People take the time to read and to comment, and they deserve the respect to have that communication. Also be aware that comments can be quoted in press, direct questions from jouranlists and similar, so please reach out to Mozilla press if you want/need to verify your statement.
It is also a long term base for a good relations with developers based on mutual respect and communication.
Mozilla Hacks is a place based on mutual respect and understanding, and the way we address each other is supposed to reflect that. We expect anyone writing or commenting to use proper laguage and refrain from insulting other people. We reserve the right to remove anything that doesn't qualify as decent behavior towards other people.
Blog posts should be added to the Mozilla Hacks blog calendar in good time before - it now resides internally in Zimbra. E-mail mozhacks [at] mozilla [dot] com for access, to have an overview of what is being planned. Everything that is to be published needs to be approved before, by Robert Nyman, Christian Heilmann or Stormy Peters - or Developer Engagement otherwise if they aren't reachable (see contact information above). We would like at least a few days notice before posting, to read through it and ensure it is both on topic and phrased in a way suitable for Mozilla Hacks.
We generally refrain from posts on Fridays, US time, since then the rest of the world have moved into weekend, meaning that we won't be available to reply to comments or handle any other feedback
Writing for Mozilla Hacks
When it comes to more detailed questions on how to format content for a blog post, which plugins are supported and more, read more in the Writing for Mozilla Hacks guidelines.
We are currently using Google Analytics, and biweekly metrics reports are sent internally.
These are general topics and areas we will cover
- Open Web
- Firefox OS
- Web APIs
- Mozilla Products (engineer perspective) - Bleeding Edge Firefox etc
- Recurring posts:
- Hacks Weekly
- Bi-weekly State of games
- Monthly - most interesting posts on Mozilla Hacks
- Monthly: Dev Derby winners
- Monthly: Interview with most recent Derby winner (unless the winner doesn't want to)
- Web Developer Toolbox: introductions to tools and libraries
- Wiki Wednesday
- State of the Docs
- Use cases
- Evaluations and guides to HTML5 Apps & games
- News in the web development world - short links, attention bits and more
- News related to MDN: doc sprints, etc.
Organization and Contact
Editor: Robert Nyman (robert@)
- Christian Heilmann (cheilmann@)
- Janet Swisher (jswisher@)
- Eric "Sheppy" Shepherd (eshepherd@)
All e-mail addresses can be reached at @mozilla.com. Please contact any of the people above or mozhacks [at] mozilla [dot] com if you have any questions.