Translate content to Dutch

[tunetheweb]

These are the core templates - without which we cannot release any translated chapters. They are in the language specific templates directory:

• base.html - @noah-vdv
• base_chapter.html- @noah-vdv
• error.html- @noah-vdv

2025

• base.html -
• base.html - foreword
• contributors.html -
• index.html -
• table_of_contents.html -

2024

• base.html -
• base.html - foreword
• contributors.html -
• index.html -
• table_of_contents.html -

2022

• base.html -
• contributors.html -
• index.html -
• table_of_contents.html -

2021

• base.html -
• base.html - foreword
• contributors.html -
• index.html -
• table_of_contents.html -

2020

• base.html - @noah-vdv
• contributors.html - @noah-vdv
• index.html - @noah-vdv
• table_of_contents.html - @noah-vdv

2019

• base.html - @noah-vdv
• contributors.html - @noah-vdv
• index.html - @noah-vdv
• table_of_contents.html - @noah-vdv

These are the chapters to be translated. They exist in the content directory:

2025

• fonts -
• webassembly -
• third-parties -
• generative-ai -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• capabilties -
• pwa -
• cms -
• ecommerce -
• page-weight -
• cdn -
• cookies -

2024

• javascript -
• markup -
• structured-data -
• fonts -
• media -
• third-parties -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• cms -
• ecommerce -
• jamstack -
• sustainability -
• page-weight -
• cdn -
• http -
• cookies -

2022

• css -
• javascript -
• markup -
• structured-data -
• fonts -
• media -
• webassembly -
• third-parties -
• interoperability -
• seo -
• accessibility -
• performance -
• privacy -
• security -
• mobile-web -
• capabilities -
• pwa -
• cms -
• jamstack -
• sustainability -
• page-weight -
• cdn -
• http -

2021

• css -
• javascript -
• markup -
• structured-data -
• media -
• webassembly -
• third-parties -
• seo -
• accessibility -
• performance -
• privacy - @VictorLeP
• security -
• mobile-web -
• capabilities -
• pwa -
• cms -
• ecommerce -
• jamstack -
• page-weight -
• compression -
• caching -
• cdn -
• resource-hints -
• http -

2020

• css -
• javascript - @noah-vdv
• seo - @noah-vdv
• markup - @noah-vdv
• accessibility - @noah-vdv
• cms - @noah-vdv
• performance - @noah-vdv
• security - @noah-vdv
• jamstack - @noah-vdv
• fonts - @noah-vdv
• mobile-web - @noah-vdv
• pwa - @noah-vdv
• http2 - @noah-vdv
• capabilities - @noah-vdv
• third-parties - @noah-vdv
• page-weight - @noah-vdv
• caching - @noah-vdv
• resource-hints - @noah-vdv
• privacy - @noah-vdv
• compression - @noah-vdv
• ecommerce - @noah-vdv
• media - @noah-vdv

2019

• javascript -
• css -
• seo -
• performance -
• http2 -
• markup -
• third-parties -
• fonts -
• accessibility - @noah-vdv
• pwa -
• cms -
• security -
• media -
• mobile-web -
• cdn -
• ecommerce -
• page-weight -
• caching -
• compression -
• resource-hints -

Additionally the following pages need translated too in the language specific templates directory:

• 2021/methodology.html -
• 2019/methodology.html - @noah-vdv
• 2020/methodology.html - @noah-vdv
• accessibility_statement.html - @noah-vdv
• accessibility_statement.html additional update - @VictorLeP Add Dutch accessibility statement translation extra piece #2596
• base_ebook.htm - @noah-vdv

There is no need to translate the chapters HTML pages as they are generated off the markdown combined with the above templates.

Please include "Makes progress on #1750" in all pull requests so a link is created from the PR to this issue.

---

Common notes for writing consistency are here: https://github.com/HTTPArchive/almanac.httparchive.org/wiki/Translators'-Guide. Feel free to edit that and/or add Dutch-specific extras by editing this comment.

Dutch specific extra advice:

[strangernr7]

So the html files don't need to be translated right? Just the files under 2020, 2019 and additional files?

[tunetheweb]

The core html files DO need to be translated.

The chapter HTMLs not shown above (e.g. performance.html) do not need to be translated as they are generated from the markdown (e.g. performance.md). We used to store these generated chapter HTML files in git, but no longer do so probably can remove the statement related to that as probably more confusing than useful. Then again if you run the site locally (see instructions in src/README.md) then it will generate these files but they can be ignored from translation point of view.

That make sense, or have a just confused you more than helped? 😀

[strangernr7]

alright, nah that helped thanks

[rviscomi]

@noah-vdv thanks for your help translating this content! I see the base templates have been checked off. Have those translations been submitted yet?

[strangernr7]

@noah-vdv thanks for your help translating this content! I see the base templates have been checked off. Have those translations been submitted yet?

No problem.
I have checked them off indeed but realized that I might have translated bits that didn't need translating and totally forgot to check if some pieces needed the <lang="en"> tags. So I'll double-check those html files and get a PR out on Thursday hopefully.

[tunetheweb]

Feel free to open a draft PR for now and I can give feedback.

To @rviscomi ’s point we normally put your name beside something you’re working on (so others don’t work on it too) but only tick it off after PR is accepted to show its “done”. I’ve updated the first comment to that now.

[tunetheweb]

BTW since you've done the base templates we're ready to send this language live so (at the risk of making this PR even bigger!) can you add Dutch to server/language.py (lines 45-54) and also add nl to supported_languages in config/2019.json and config/2029.json?

[strangernr7]

Should I translate content such as First Input Delay or keep it as is?