Confirmed users
1,021
edits
(→Images and video: updates) |
(→Writers' Guidelines: images updates) |
||
Line 28: | Line 28: | ||
*It autodetects a wide variety of programming languages | *It autodetects a wide variety of programming languages | ||
*Format: <pre><code class="js">keep on rocking the free web foo</code></pre> | *Format: <pre><code class="js">keep on rocking the free web foo</code></pre> | ||
==== Images, captions, and video ==== | ==== Images, captions, and video ==== | ||
Line 45: | Line 38: | ||
*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'''. | ||
* For video, here's a format that works: [embed]YOUR VIDEO EMBED URL[/embed] | |||
==== Links: We like links! ==== | |||
*We like them best in the body of the article, rather than served as relative links with a separate Reference or Footnotes section at the bottom | |||
*Please use the target="_blank" argument in your URL call. In the WP-editor you can "Open link in a new window/tab" when you use the "Insert/edit link" UI. | |||
*Look for places to link to relevant technical content from Mozilla Developer Network (e.g. articles about new features, functions, or APIs) or Wikipedia (esp for technical acronyms). Don't assume your readers know where to look. | |||
*Length: Most Hacks articles fall in the range of 800-1500 words. Some run longer, but if they run much longer we'll encourage you to write a series rather than a single post. | |||
==== Markdown ==== | ==== Markdown ==== |