Edit 2020 Chapters

[tunetheweb]

Part I. Page Content

• - Chapter 1: CSS - @bazzadp Copy edit of 2020 CSS chapter #1846
• - Chapter 2: JavaScript - @rviscomi 2020 JavaScript edits #1737
• - Chapter 3: Markup - @rviscomi Edit 2020 Markup chapter #1435 and 2020 Markup chapter editing #1604
• - Chapter 4: Fonts - @bazzadp Copyedit of Fonts 2020 chapter #1816 and Close out final 2020 Fonts Chapter TODOs #1868
• - Chapter 5: Media - @bazzadp Media 2020 chapter #1882
• - Chapter 6: Third Parties - @bazzadp - Copyedit Third Parties 2020 #1877

Part II. User Experience

• - Chapter 7: SEO - @rviscomi
• - Chapter 8: Accessibility - @bazzadp - Copyedit of 2020 Accessibility chapter and addition of more figures #1752
• - Chapter 9: Performance - @bazzadp - Copyedit of 2020 Performance chapter #1622
• - Chapter 10: Privacy - @bazzadp - Copyediting of the Privacy chapter #1672 and Update 2020 Privacy chapter for CDNs and Hosting categories #1935
• - Chapter 11: Security - @bazzadp - Copyedit 2020 Security chapter #1927
• - Chapter 12: Mobile Web - @exterkamp - Mobile Web 2020 edits #1758
• - Chapter 13: Capabilities - @rviscomi Edit 2020 Capabilities chapter #1492
• - Chapter 14: PWA - @bazzadp - Copyedit 2020 PWA chapter #1924

Part III. Content Publishing

• - Chapter 15: CMS - @bazzadp - Copyedit of the CMS 2020 Chapter #1624
• - Chapter 16: Ecommerce - @bazzadp - Ecommerce 2020 chapter #1891
• - Chapter 17: Jamstack - @bazzadp - Copyedit of Jamstack chapter #1665 and Add Nuxt and Docusauraus to Jamstack 2020 chapter #1938

Part IV. Content Distribution

• - Chapter 18: Page Weight - @bazzadp - Copyedit of the 2020 Page Weight chapter #1894
• - Chapter 19: Compression - @exterkamp - Compression 2020 edits #1688 Compression 2020 more edits #1911
• - Chapter 20: Caching - @bazzadp - Copyedit Caching 2020 #1915
• - Chapter 21: Resource Hints - @exterkamp - Resource Hints 2020 edits #1664
• - Chapter 22: HTTP/2 - @rviscomi - HTTP/2 edits #1618

[tunetheweb]

Same rules as last time @HTTPArchive/editors - grab a chapter when you see one free and claim it by tagging your name next to the first issue and then submit a PR with the original authors. Links to chapters available in our issue tracker

[rviscomi]

Pro tip for editors who spot something that should be changed but the fix isn't ready yet (for example a link to an unlaunched chapter), use a Jinja comment starting with TODO so it's annotated in the markdown file, easily discoverable, and not included in the HTML output.

{# TODO: Link directly to the relevant Accessibility section. #}
We identified 2,863 different values for the `lang` attribute on the `html` start tag (compare that to the [7,117 spoken languages](https://www.ethnologue.com/guides/how-many-languages) as per Ethnologue). Almost all of them, [according to the Accessibility chapter](./accessibility), seem valid.

I've added this to the Editor's Guide wiki

[tunetheweb]

Tagging those that expressed an interest in editing in #922 (👋 again @rachellcostello ). If anyone else is interested (@HTTPArchive/editors ?) then feel free to add your self to Assignees.

The Capabilities chapter is good to go for editing if anyone wants to grab it?

[tunetheweb]

Added two new suggestions to Editors Guide:

• Check previous years chapters table of contents and flag to authors if any messing pieces, to ensure they didn't accidentally leave out an important section
• Check print version (add ?print to URL) to ensure all images load (check for console errors is the easiest way of checking this).

[rviscomi]

@bazzadp @rachellcostello CMS is ready for editing, would either of you like to take that one?

[tunetheweb]

HTTP/2 is ready for editing.

I'll have a look at CMS in next day or two if no one else grabs it.

[rviscomi]

@HTTPArchive/editors Resource Hints is now ready for editing

[tunetheweb]

@HTTPArchive/editors HTTP/2 and SEO is ready for editing

[rviscomi]

Added a note to the editors' wiki about using the numeric class on tabular figures. See this before and after:

It's a minor change but right-aligning makes the decimal points line up and is easier to read.

To make this conversion, I'll "copy outer HTML" of the rendered table in DevTools, replace the markdown table with it, and add the class="numeric" to each td that needs it. Don't forget to remove the markdown class from the figure!

Before:

<figure markdown>
| Protocol | Desktop | Mobile |
| -------- | ------- | ------ |
| HTTP/1.1 | 36.05%  | 34.04% |
| HTTP/2   | 63.95%  | 65.96% |
<figcaption>...</figcaption>
</figure>

After

<figure>
  <table>
    <thead>
      <tr>
        <th>Protocol</th>
        <th>Desktop</th>
        <th>Mobile</th>
      </tr>
    </thead>
    <tbody>
      <tr>
        <td>HTTP/1.1</td>
        <td class="numeric">36.05%</td>
        <td class="numeric">34.04%</td>
      </tr>
      <tr>
        <td>HTTP/2</td>
        <td class="numeric">63.95%</td>
        <td class="numeric">65.96%</td>
      </tr>
    </tbody>
  </table>
  <figcaption>...</figcaption>
</figure>

[tunetheweb]

@HTTPArchive/editors PWA and Jamstack are ready for editing.

[tunetheweb]

Compression and Caching ready for editing.