Devrel/Hacks: Difference between revisions

Mozilla Hacks is a pragmatic blog for designers, developers, and people who make the web. We cover Firefox development, and the varied engineering work that tests, releases, supports and secures the browser. Melissa Thermidor is Managing Dditor.
(updates)
(Mozilla Hacks is a pragmatic blog for designers, developers, and people who make the web. We cover Firefox development, and the varied engineering work that tests, releases, supports and secures the browser. Melissa Thermidor is Managing Dditor.)
Line 1: Line 1:
Info about the Hacks blog and how you can participate.  
[https://hacks.mozilla.org Mozilla Hacks] is a pragmatic blog for designers, developers, deciders and people who make the web. We cover Firefox development, and the varied engineering work that tests, releases, supports and secures the browser. Hacks also publish pragmatic explanations of emerging standards and new APIs, reports on tooling for website and web platform development, as well as news from the MDN Web Docs team, where we document the web, and past events and activities of the Developer Relations team. Mozilla Hacks is managed by the Community team and
[https://people.mozilla.org/p/melissathermidor Melissa Thermidor] is Managing Editor.  


[https://hacks.mozilla.org Mozilla Hacks] is a pragmatic blog for designers, developers, deciders and people who make the web. We cover Firefox development, as well as website and web platform development from a technical perspective for people who make websites (or apps or services). Mozilla Hacks is managed by the Developer Relations team. [https://mozillians.org/en-US/u/havi/ Havi Hoffman] is managing editor.  
We also manage the [https://www.youtube.com/user/mozhacks Mozilla HacksYouTube Channel] as well as the [https://twitter.com/mozhacks Mozilla Developer] and [https://twitter.com/mozdevnet MDN Web Docs] Twitter accounts. Please contact Melissa Thermidor if you need content shared from these social media accounts.  


We also manage the [https://www.youtube.com/user/mozhacks MozHacksYouTube Channel] and the [https://twitter.com/mozhacks @mozhacks twitter account]. Please contact Melissa Thermidor if you need a tweet or a RT from @mozhacks or @mozdevnet.  
Everyone has a voice and we would like you to use our platform to connect with developers. We are seeking technical content, opinions, and stories from many different viewpoints.
 
If your work touches the work of developers, but you're not sure what to write about, let's chat directly about telling your story. Happy to meet in our new reality of Zoom ‘real-time’ or address questions async on Slack, or email. Sometimes a conversation can clarify a storyline, or shed light on how to most effectively share your new learning or key idea.
 
Engineers have asked, "I'm a software developer. I'm not a writer. Can you help?"
 
Yes, we can. We are happy to meet people where they are, and work 1:1 with you, your topic, and your idea.


==Writers' Guidelines==
==Writers' Guidelines==
==== Workflow and review process for Hacks posts ====
==== Workflow and review process for Hacks posts ====
*If you have a timely and pragmatic original post on a technical topic of interest (Firefox, Mozilla, JavaScript, CSS, web design and development, the web platform and advanced development, Emerging Tech projects), we'd love to hear from you. Please contact Havi Hoffman by email or Slack with a brief description of your article.
*If you have a timely and pragmatic original post on a technical topic of interest (Firefox, Mozilla, JavaScript, CSS, web design and development, the web platform and advanced development), we'd love to hear from you. Please contact Melissa Thermidor by email or Slack with a brief description of your article.


*Workflow: Please share your first draft in a Gdoc, and help us identify key stakeholders/approvers/review who will need to review and share feedback. Once all comments are in the Gdoc and have been resolved, the post author is responsible for adding the draft directly to wordpress. We'll establish a publication date, share with all relevant social channels, and prior to publication we do a final copyedit and link check in the wordpress post.  
*Workflow: Please share your first draft in a Google Doc, and help us identify key stakeholders/approvers/review who will need to review and share feedback. Once all comments are in the Gdoc and have been resolved, the post author is responsible for adding the draft directly to WordPress. Don't worry about copyediting, SEO, etc - the managing editor will make these changes. We'll establish a publication date, share with all relevant social channels, and prior to publication we do a final copyedit and link check in the WordPress post.  


*We typically publish 2-3 times weekly on Tues - Thur, 8am pt. We avoid scheduling more than one article on any given day.
*We typically publish 1-2 times weekly on Tues - Thur, 8am pt. We avoid scheduling more than one article on any given day.


* When you write for Hacks, you are welcome to cross-post to another blog or Medium channel/account, but we ask that you DO NOT publish until we have published on Hacks.
* When you write for Hacks, you are welcome to cross-post to another blog or Medium channel/account, but we ask that you DO NOT publish until we have published on Hacks.
Line 26: Line 33:


==== Images, captions, and video ====  
==== Images, captions, and video ====  
*Author bio image: You can connect a gravatar.com image with the email address listed in Wordpress to display an author photo or image alongside your bio.
*Author bio image: You can connect a gravatar.com image with the email address listed in WordPress to display an author photo or image alongside your bio.
*Images in a post: Upload via "Add media" link in Wordpress. WP will host your image. Use the upload link to embed video also. Please don't host images externally.  
*Images in a post: Upload via "Add media" link in Wordpress. WP will host your image. Use the upload link to embed video also. Please don't host images externally.  
*IMPORTANT A11y requirement: Don't forget to include a description of the image in the alt= field provided, for screenreaders. A post is not complete until alt text is available for '''every image'''.  
*IMPORTANT A11y requirement: Don't forget to include a description of the image in the alt= field provided, for screenreaders. A post is not complete until alt text is available for '''every image'''.  
Line 43: Line 50:


== Editorial Calendar ==
== Editorial Calendar ==
We maintain a Hacks Editorial calendar on Mozilla's gcal - if you are Mozilla staff you can access it here: [https://calendar.google.com/calendar/embed?src=mozilla.com_h1vjme6vi1m7o3f05vv32qa2a4@group.calendar.google.com&ctz=America/Los_Angeles Mozilla Hacks Editorial calendar] If you are an NDA'ed Mozillian who needs access, you may request it by pinging Havi. We're working on an Airtable view. Please ping if you have a Mozilla Airtable account and this is of interest.
We maintain a Hacks Editorial calendar on Mozilla's GCal - if you are Mozilla staff you can access it here: [https://calendar.google.com/calendar/embed?src=mozilla.com_h1vjme6vi1m7o3f05vv32qa2a4@group.calendar.google.com&ctz=America/Los_Angeles Mozilla Hacks Editorial calendar] If you are an NDA'ed Mozillian who needs access, you may request it by sending a message to Melissa Thermidor.
3

edits