Publish vision par ordinateur apprentissage profond pt1

[anisa-hawes]

Preparing files for publication.

Closes #3752

Checklist

• Assign yourself in the "Assignees" menu
• Add the appropriate "Label"
• If this PR closes an Issue, add the phrase Closes #ISSUENUMBER to your summary above
• Ensure the status checks pass: if you have difficulty fixing build errors, please contact our Publishing Manager @anisa-hawes
• Check the Netlify Preview: navigate to netlify/ph-preview/deploy-preview and click 'details' (at right)
• Assign at least one individual or team to "Reviewers"
  • if the text needs to be translated, please follow the translation request guidelines, then assign the relevant language team(s) as "Reviewers" and tag both the team as well as the managing editor in your PR.

[anisa-hawes]

Bonjour Marie @marie-flesch,

I’ve staged vision-par-ordinateur-apprentissage-profond-pt1 for publication. You can read it through in Preview and let me know if you notice anything which you'd like to adjust.

Please note: Unfortunately, I've encountered a problem with the nbviewer link system that we use to render our codebooks. I've described the problem (as well as I understand it) in an Issue #3757. The short version is that the accompanying codebook should look like this but instead looks like this.

This might be a temporary problem, so we could wait and re-check? Let me know your thoughts.

In the meantime, I'll investigate an alternative solution.

Thank you for your patience,
Anisa

[marie-flesch]

Looks good!

[anisa-hawes]

Dear Marie,

The problem with the codebook rendering with nbviewer seems to be solved, so we are able to use our usual system and I have updated the links throughout.

https://nbviewer.org/github/programminghistorian/jekyll/blob/gh-pages/assets/vision-par-ordinateur-apprentissage-profond-pt1-2/vision-par-ordinateur-apprentissage-profond-pt1-2.ipynb

I appreciate your patience while I have resolved the various other build errors here – there have been GitHub outages during the past few days but everything is back up and running now 🙂