Checklists translations

Translations

The following can be used as a template for our final comment in a translated lesson's Issue on ph-submissions:

Hello @ManagingEditor,

This lesson is ready for your final review + transfer to Jekyll.

• Preview:

EN: http://programminghistorian.github.io/ph-submissions/en/drafts/translations/lesson-file-name-here
ES: http://programminghistorian.github.io/ph-submissions/es/borradores/traducciones/lesson-file-name-here
FR: http://programminghistorian.github.io/ph-submissions/fr/en-cours/traductions/lesson-file-name-here
PT: http://programminghistorian.github.io/ph-submissions/pt/esbocos/traducoes/lesson-file-name-here

Publisher's sustainability + accessibility actions:

• Typesetting
• Addition of Perma.cc links
• Addition of alt-text for all figures
• Check/resize images
• Check/adjust image filenames
• Receipt of translator's copyright agreement
• Request doi

Editorial input to YAML:

• Translation of avatar_alt:
• Translation of abstract:
• Translation of author(s) bio for ph_authors.yml

Files to be transferred to Jekyll:

EN:

• .md file: /en/drafts/translations/lesson-file-name-here.md
• images: /images/lesson-file-name-here
• assets: /assets/lesson-file-name-here

ES:

• .md file: /es/borradores/traducciones/lesson-file-name-here.md
• images: /images/lesson-file-name-here
• assets: /assets/lesson-file-name-here

FR:

• .md file: /en-cours/traductions/lesson-file-name-here.md
• images: /images/lesson-file-name-here
• assets: /assets/lesson-file-name-here

PT:

• .md file: /esbocos/traducoes/lesson-file-name-here.md
• images: /images/lesson-file-name-here
• assets: /assets/lesson-file-name-here

Promotion:

• Prepare announcement post (using template)
• Prepare x2 future posts for our Twitter/Mastodon Bot