Proposta de Lição: Investigar a literatura lusófona através dos tempos usando a Literateca

[ericbrasiln]

O Programming Historian em Português recebeu uma proposta de lição original com o título provisório "Investigar a literatura lusófona através dos tempos usando a Literateca".

Para promover uma publicação oportuna, propomos que a lição seja entregue em meados de março de 2024. A autora entrará em contato com o editor com antecedência caso não consiga cumprir a data de entrega e precise de uma prorrogação.

Se a lição não for entregue, o editor tentará entrar em contato com a autora da lição. Se nenhuma notícia for recebida, a issue será fechada. Ela poderá ser reaberta no futuro, a pedido da autora.

O contato principal para esta lição é, por enquanto, @ericbrasiln. Se ocorrer algum problema, a autora pode entrar em contato com o mediador do PH em português (Luis Ferla - http://programminghistorian.org/pt/equipe).

[ericbrasiln]

@dianamsmpsantos já compartilhou o pacote de submissão comigo, contendo texto markdown, figuras e recursos de dados. Nossa equipe de Publicação (@anisa-hawes e @charlottejmc) processará os novos materiais da lição em setembro e preparará uma prévia do rascunho inicial. Eles discutirão qualquer dúvida com o colaborador e postarão um comentário nesta questão para fornecer a localização de todos os arquivos-chave, bem como um link para a prévia, onde os colaboradores poderão ler a lição conforme o rascunho avança.

Em breve teremos a indicação do/a editor/a responsável pela lição.

[anisa-hawes]

Thank you, @ericbrasiln!

@charlottejmc and I will process these submission materials and set up the lesson preview for you this week ✨

[charlottejmc]

Olá @ericbrasiln e @dianamsmpsantos,

Pode encontrar os ficheiros principais aqui:

• .md: /pt/esbocos/originais/investigar-literatura-lusofona-literateca.md
• images: /images/investigar-literatura-lusofona-literateca
• assets: /assets/investigar-literatura-lusofona-literateca

Pode consultar a pré-visualização da lição aqui:

• http://programminghistorian.github.io/ph-submissions/pt/esbocos/originais/investigar-literatura-lusofona-literateca

---

Dear @dianamsmpsantos,

There are a few small things I noticed while setting up your submission, which I have outlined below:

• The code is looking a little strange at lines 162-174; 180-190; 234-246; and 272-286 (in the preview, paragraphs 41-47; 50-55; 71-78; and 88-96). Did you mean to separate the code individually line by line, or were you hoping for them to appear as code blocks instead? If you'd like them to appear as code blocks, I can make that change for you. In general, you might find it easier to read and write your code by simply using single backticks around short bits of code (in-line, or single lines of code).
• I notice you have a list of assets, but none of these files are linked to directly from within the lesson (so that readers can access them). Would you be able to add the links in where relevant? You can point directly to the files on Github, for example like this: [distribuicaoObra.tsv](https://github.com/programminghistorian/ph-submissions/blob/gh-pages/assets/investigar-literatura-lusofona-literateca/distribuicaoObra.tsv).
• Finally, I saw that you provided 'alt-text' for all images, thank you! Unfortunately, it is currently a little under-descriptive, so I'd like to ask whether you might be able to try adding some more information to them.

Alt-text enables screen readers to read the information conveyed in the images for people with visual impairments, different learning abilities, or who cannot otherwise view them, for example due to a slow internet connection. It's important to say that alt-text should go further than repeating the figure captions.

We have found Amy Cesal's guide to Writing Alt Text for Data Visualization useful. This guide advises that alt-text for graphs and data visualisations should consist of the following:

alt="[Chart type] of [data type] where [reason for including chart]"

What Amy Cesal's guide achieves is prompting an author to reflect on their reasons for including the graph or visualisation. What idea does this support? What can a reader learn or understand from this visual?

The Graphs section of Diagram Center's guidance is also useful. Some key points (relevant to all graph types) we can take away from it are:

• Briefly describe the graph and give a summary if one is immediately apparent
• Provide any titles and axis labels
• It is not necessary to describe the visual attributes of the graph (colour, shading, line-style etc.) unless there is an explicit need
• Often, data shown in a graph can be converted into accessible tables

For general images, Harvard's guidance notes some useful ideas. A key point is to keep descriptions simple, and adapt them to the context and purpose for which the image is being included.

Would you feel comfortable redrafting the alt-text for each of the figures? This is certainly a bit time-consuming, but we believe it is very worthwhile in terms of making your lesson accessible to the broadest possible audience. We would be very grateful for your support with this.

Thank you!!