Translate content to Spanish

[JMPerez]

trafficstars

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

• [x] base.html -
• [x] base_chapter.html-
• [x] error.html-

2024

• [x] base.html -
• [ ] base.html - foreword
• [x] contributors.html -
• [x] index.html -
• [x] table_of_contents.html -

2022

• [x] base.html -
• [x] contributors.html -
• [x] index.html -
• [x] table_of_contents.html -

2021

• [x] base.html -
• [ ] base.html - foreword
• [x] contributors.html -
• [x] index.html -
• [x] table_of_contents.html -

2020

• [x] base.html -
• [ ] base.html - foreword added later
• [x] contributors.html -
• [x] index.html -
• [x] table_of_contents.html -

2019

• [x] base.html -
• [x] contributors.html -
• [x] index.html -
• [x] table_of_contents.html -

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

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 -
• [x] seo - @carloscastromx
• [ ] accessibility -
• [ ] performance -
• [x] privacy - @decrecementofeliz
• [ ] 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 - @nucliweb
• [ ] privacy -
• [ ] security -
• [ ] mobile-web -
• [ ] capabilities -
• [ ] pwa -
• [ ] cms -
• [ ] ecommerce -
• [ ] jamstack -
• [ ] page-weight -
• [ ] compression -
• [ ] caching -
• [ ] cdn -
• [ ] resource-hints -
• [ ] http -

2020

• [ ] css -
• [x] javascript - @alangdm
• [x] seo - @carloscastromx
• [ ] markup -
• [ ] accessibility -
• [ ] cms -
• [ ] performance -
• [ ] security -
• [ ] jamstack -
• [ ] fonts -
• [ ] mobile-web -
• [ ] pwa -
• [x] http2 - @moniloria
• [ ] capabilities -
• [ ] third-parties -
• [ ] caching -
• [ ] resource-hints -
• [ ] privacy -
• [ ] compression -
• [ ] ecommerce -
• [ ] media -

2019

• [x] javascript - @c-torres
• [ ] Slight tweak to JavaScript chapter as completed in #624
• [x] css - @c-torres
• [ ] seo -
• [x] performance - @JMPerez
• [ ] http2 -
• [x] markup - @c-torres
• [ ] third-parties - @garcaplay
• [x] fonts - @c-torres
• [ ] accessibility -
• [ ] pwa -
• [ ] cms -
• [ ] security - @c-torres
• [x] media - @garcaplay
• [ ] mobile-web -
• [ ] cdn -
• [x] ecommerce - @JMPerez
• [ ] page-weight -
• [ ] caching -
• [ ] compression -
• [ ] resource-hints -

Additionally the following pages need translated too in the language specific templates directory, but less important than core templates and chapters:

• [x] accessibility_statement.html -
• [ ] accessibility_statement.html additional update -
• [ ] base_ebook.html -
• [ ] 2021/methodology.html -
• [ ] 2020/methodology.html -
• [ ] 2019/methodology.html -

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

Please include "Makes progress on #498 " 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 Spanish-specific extras by editing this comment.

Spanish-specific extra advice:

• None yet

[c-torres]

Should we include the specific pages? Like Table of Contents, Methodology, etc.

[rviscomi]

@c-torres there are still some changes happening to those pages so let's leave those for last.

[c-torres]

Working on the JavaScript chapter.

[c-torres]

Working on the CSS chapter.

[tunetheweb]

Working on the CSS chapter.

Hey @c-torres just so you're aware, very shortly (I hope - nudge, nudge @rviscomi !!😉 ) we will be merging #511 which contains a change of format for the diagrams and more descriptive text for them.

We already did the JavaScript chapter and I checked and you got the latest version so that's cool. However unfortunately we will need you guys to revist the other chapters you've already done.

So before you submit the CSS chapter you might be best to double check master to ensure you've got the latest diagram markdown. Or alternatively take the source from the figures_new_format branch under the assumption it will be merged.

Sorry about this change, but I thought it would be worthwhile giving you the heads up to this as know there are a lot of figures in the CSS chapter!

[c-torres]

No worries, thanks for the heads up, really appreciated.

[tunetheweb]

That's now merged to master @c-torres and will shortly be updated in prod. So you're good to grab the latest version. It was the same that was in the branch if you've already started on that. Will raise a separate issue for the other chapters already done to have another look over.

[c-torres]

Submitted a PR for CSS translation. Will continue working on Media Chapter.

[tunetheweb]

Hey @c-torres @JMPerez @taytus !

We’re now in the position to launch chapters that have been translated without having to wait for all chapters to be translated.

To do that however we do need base_chapter.html translated and also probably a good idea to review base.html. These are both quite short so a lot easier to translate than the chapters.

Would any of you have the time to have a look? Would be great to get the chapters you’ve worked on out there available to the public and might even encourage others to help out with the remaining chapters.

[taytus]

Hello @tunetheweb , unfortunately, I'm totally swamped and won't be able to help at this moment. I'm sorry 😔

[rviscomi]

We'd still love to see the 2019 chapters translated into Spanish, if anyone's interested to make that happen. And translating all of the chapters would be an amazing milestone to reach, because then we can release the fully translated ebook, as we've done for Japanese:

[tunetheweb]

Welcome @moniloria to team español!

I've updated the chapters that are available in the first comment so put your name besides the one you want to translate and off you go. Original English is in src/content/en/2020/ and should be translated and saved to src/content/es/2020/ and a pull request opened for it. I'll review it from a technical perspective and hopefully one of your fellow translators will look at the Spanish. Then we merge, release, and bask in the ever-lasting love of the Spanish web dev community 😁

Any questions give me a shout!

[moniloria]

Welcome @moniloria to team español!

I've updated the chapters that are available in the first comment so put your name besides the one you want to translate and off you go. Original English is in src/content/en/2020/ and should be translated and saved to src/content/es/2020/ and a pull request opened for it. I'll review it from a technical perspective and hopefully one of your fellow translators will look at the Spanish. Then we merge, release, and bask in the ever-lasting love of the Spanish web dev community 😁

Any questions give me a shout!

Hi @tunetheweb , thanks for the welcome! I have started working with GitHub recently so it might take me a bit to finish this first chapter, I have found the Git Guide and all good! but I have noticed there is no Spanish 2020 folder (src/content/es/2020/) should I create it? Or should I focus on the translation of 2019 version?

[tunetheweb]

GitHub only creates the folder if there are any files and we haven’t translated any 2020 content yet - just finished it in English to be honest! - so that’s why it doesn’t exist yet. So yes please create it. Would prefer to concentrate on 2020 content and only do 2019 after that since it’s the most recent and therefore interesting to readers!

[nucliweb]

Hi @tunetheweb I would like to help with Spanish translation.

[tunetheweb]

Good stuff @nucliweb - tag a chapter with your name in the first comment and away you go!

[nucliweb]

Good stuff @nucliweb - tag a chapter with your name in the first comment and away you go!

@tunetheweb I can't edit the first comment to add my name.

[tunetheweb]

Just sent you a GitHub invite to the team. When you accept that you should be able to edit it.

[alangdm]

I will try to do 2020's javascript article

[tunetheweb]

Great stuff. Let us know if you have any questions. The first chapter can always take a bit longer as you get used to the content/format/process but always willing to help!

[excellenseo]

Hi @tunetheweb , let me know where can I help.

[tunetheweb]

@excellenseo edit the first item to put your name against one of the ones that are not done yet and away you go! Translate and submit a PR for review. They are in rough popularity order.

There was a foreword added to src/templates/en/2020/base.html which doesn't exist in the es version and maybe that would be a nice easy one to start with before you tackle a full chapter?

After that maybe the 2020 SEO one tempts you, given your username? 😀

[tunetheweb]

Actually sorry, I see @carloscastromx has nabbed the SEO one already! So either ask them if they're willing to trade or grab one of the others that haven't been assigned yet.

[excellenseo]

@tunetheweb I will start with the base.html and will continue with http2. @carloscastromx let me know if you need help for the SEO chapter.

[tunetheweb]

Looks like http2 is already done for 2020. And think we should work on 2020 now as less people interested in 2019. So I'd pick another chapter if I were you. Unless you're really interested in HTTP/2, in which case go for it.

[excellenseo]

Oh I was looking at 2019 instead of 2020. I selected markup. Thanks @tunetheweb

[carloscastromx]

@tunetheweb I will start with the base.html and will continue with http2.

@carloscastromx let me know if you need help for the SEO chapter.

Will do!

[tunetheweb]

We added a small note to our Accessibility Statement about colour contrast issues:

https://github.com/HTTPArchive/almanac.httparchive.org/blob/14f85122c88d14ee1f8dd0474479424338766625/src/templates/es/accessibility_statement.html#L69-L71

Would be great if someone could translate this. Very small and easy!

[nucliweb]

Hi @tunetheweb I can help with the Spanish translation 2021, and I would like to start with performance, resource-hints, javascript and webassembly sections.

[tunetheweb]

Great news @nucliweb ! Edit the first comment to stick your name by one of them to "claim" that translation and away you go. Maybe don't claim all 4 of them initially to give any others a chance.