Confirmed users
1,021
edits
(→Completed Posts: removing, obsolete) |
(updates) |
||
| Line 1: | Line 1: | ||
Info about the Hacks blog and how you can participate. | Info about the Hacks blog and how you can participate. | ||
[https://hacks.mozilla.org Mozilla Hacks] is a pragmatic blog for people who make the | [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 MozHacks YouTube Channel] and the [https://twitter.com/mozhacks @mozhacks twitter account]. Please contact [https://mozillians.org/en-US/u/Flaki/ Istvan 'Flaki' Szmozsanszky] or Havi if you need a tweet or a RT from @mozhacks. | We also manage the [https://www.youtube.com/user/mozhacks MozHacks YouTube Channel] and the [https://twitter.com/mozhacks @mozhacks twitter account]. Please contact [https://mozillians.org/en-US/u/Flaki/ Istvan 'Flaki' Szmozsanszky] or Havi if you need a tweet or a RT from @mozhacks. | ||
| Line 7: | Line 7: | ||
==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 | *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 via 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 | *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. | ||
*We typically publish 2-3 times weekly on Tues - Thur, 8am pt. | *We typically publish 2-3 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 | * 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. | ||
==== House Style ==== | ==== House Style ==== | ||
*We respect sentence case (EU style) and Title Case (US style) titles. British and Canadian authors are welcome to use British English spelling. (We are a global, geo-distributed organization, right?) | *We respect sentence case (EU style) and Title Case (US style) titles. British and Canadian authors are welcome to use British English spelling. (We are a global, geo-distributed organization, right?) | ||
*Please do not use H1 headers. Use H2 for section headers, H3 for sub-headers. Please do NOT include links in headers. They will be removed. | *Please do not use emoji in titles, they break on some platforms. Also, please do not use H1 headers. Use H2 for section headers, H3 for sub-headers. Please do NOT include links in headers. They will be removed. | ||
==== Code syntax for Hacks posts ==== | ==== Code syntax for Hacks posts ==== | ||
| Line 43: | Line 43: | ||
== 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 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. | ||