Issue 1995 #2452
Issue 1995 #2452
Conversation
Simplifying YAML to the minimum requirements for initial submission.
Simplifying YAML to the minimum requirements for initial submission.
Simplifying YAML to the minimum requirements for initial submission.
Simplifying YAML to the minimum requirements for initial submission.
Correcting typing error. Adding number 2, instead of repeating 1.
|
Hello @rivaquiroga. Just to note this update in connection to our conversation last week. |
ZoeLeBlanc
left a comment
ZoeLeBlanc
left a comment
There was a problem hiding this comment.
This all looks great to me! Assuming you'll be adding in documentation for adding in these other metadata yaml fields for managing editors and wondering if we need to discuss whether translations need more initial fields or not? Will MEs know that a lesson is a translation? Is that something we need to add into our process for bringing over files? Regardless think you can go ahead with these updates! Thanks @anisa-hawes
|
Thank you @ZoeLeBlanc. Yes, I think we meet our key objective which is to reduce errors when new submissions are uploaded. I'll note this into the re-draft guidelines and make a note about translations too. I will also raise this at the meeting of MEs in January #2346 |
I am updating the lesson templates, simplifying the YAML to the minimum + upper three dashes --- + authors: with the understanding that editors / or technical editor will add in the remaining fields later in the workflow:
This change aims to reduce early-phase errors for authors and editors, and updates en/lesson-template.md, es/plantilla-leccion.md, fr/modele-tuto.md, and pt/licoes-modelo.md.
Closes #1995
Checklist
if the text needs to be translated, assign the relevant language team(s) as "Reviewers" and tag both the team as well as the managing edtor in your PR. Please follow the translation request guidelines when writing your PR descriptionCloses #ISSUENUMBERto the description aboveIf you are having difficulty fixing build errors, first consult https://github.com/programminghistorian/jekyll/wiki/Making-Technical-Contributions carefully, especially "Common Build Errors". Then contact the technical team if you need further help.