Merge branch 'gh-pages' into publish-introduccion-a-tei-1

Author: anisa-hawes

_data/ph_authors.yml

@@ -116,8 +116,9 @@
   twitter: mariajoafana
   github: mariajoafana
   orcid: 0000-0003-2652-5799
-  team: true
+  team: false
   team_start: 2016
+  team_end: 2025
   institution: Universidad de los Andes, Colombia
   sortname: Afanador-Llach
   affiliation:

_posts/2025-08-06-chamada-aberta-para-propostas.md

@@ -11,7 +11,7 @@ categories: posts
 A [edição em português do _Programming Historian_](/pt/licoes/) está com chamada aberta para propostas de novas lições originais ou traduções para publicação em 2025-6.
 
 **Início das submissões**: 6 de agosto 2025   
-**Encerramento das submissões**: 31 de outubro 2025
+**Encerramento das submissões**: 31 de dezembro 2025 (_prazo prorrogado_)
 
 ## O que é uma lição do *Programming Historian*?
 

_posts/2025-10-30-enablar-call-for-participants.md

@@ -0,0 +1,123 @@
+---
+title: Call for Participation - ENABLAR
+authors: 
+- Anisa Hawes
+- James Baker
+layout: post
+categories: posts 
+---
+
+<p><figure><img src="/images/blog/ENABLAR/ENABLAR-banner.jpg" alt="Banner showing Jisc and Programming Historian logos alongside the project wordmark for the ENABLAR project, which reads ENABLAR, ENABling Library and Archive participation in digital Research co-learning communities"/><figcaption></figcaption> </figure></p>
+
+{% include toc.html %}
+
+
+_Programming Historian_ and Jisc are delighted to announce a new shared investment: **ENABLAR** - **ENAB**ling **L**ibrary and **A**rchive participation in digital **R**esearch co-learning communities.
+
+## What is ENABLAR?
+
+**ENABLAR** is a new Jisc-funded project from _Programming Historian_ that will **encourage participation** and **facilitate co-production** to **empower co-learning communities**. It will bring **library and archive practitioners** into dialogue with **digital humanities researchers**, creating opportunities for **knowledge exchange**, **skills development**, and **network building**. 
+
+- Want to develop your technical writing skills?  
+- Keen to learn from cross-disciplinary peers?  
+- Interested in co-authoring a _Programming Historian_ lesson?
+  
+If so, we’d love to hear from you. We’re inviting participation from those interested in forming a **cross-disciplinary cohort** who, over the next 10 months, will have the opportunity to **build partnerships**, **exchange insights**, and **develop the skills** needed to **co-produce** practical, accessible, sustainable lessons that support computational processing, discovery, or analysis of digital library and archive collections.
+
+
+## How will it work?
+
+The **ENABLAR** project will evolve through three phases: Phase 1: **Gather**, Phase 2: **Collaborate**, Phase 3: **Publish**. 
+
+**Phase 1: Gather**  
+- Happening right **now**. Through this call, we will gather ~10 participants as our cohort, balancing representation across library and archives professionals and digital humanities researchers.
+
+**Phase 2: Collaborate**  
+- Collaboration is central to the project, and during **December 2025** we’ll facilitate two webinars to teach effective, sustainable technical writing, and create partnerships for cross-disciplinary co-authorship.
+- As you begin writing, we’ll support your progress through an online programme of lesson development workshops and writing sprints (**January-March 2026**).
+
+**Phase 3: Publish**  
+- Through **April and May 2026**, we’ll host community review workshops to share and test **ENABLAR** lessons-in-progress. These will provide opportunities for the cohort to benefit from broader feedback, as well as each other’s - we’ll invite new voices to join us from the library and archives sector and the digital humanities research community, also seeking expressions of interest for participation in a formal open peer review process. 
+- **ENABLAR** participants will be invited to submit their drafts to _Programming Historian in English_ for consideration in **June 2026**.  
+- From **July 2026** **ENABLAR** lessons selected for development by our editorial team will be guided through open peer review towards first publication in [our English-language journal](/en/lessons/). If not selected for development, we’ll support the publication of your lesson as [grey literature](https://en.wikipedia.org/wiki/Grey_literature). All lessons will be published under an [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/deed.en) license.
+
+
+## Who can participate?
+
+We’re seeking a mixed cohort of participants from across the library and archive sector, and digital humanities research community. 
+- Maybe you’re a **librarian** who has always signposted communities towards _Programming Historian_’s lessons, but never found time to develop your own computational research skills?
+- Or an **archivist** responsible for a growing digital collection, seeking to support researchers to use computational methods to analyse or interact with archival data?
+- Perhaps you’re a **Research Software Engineer** working with cultural collections, keen to apply software engineering principles to support and enhance reader services and collections research?
+- Are you a **technician** who builds or maintains tools for data management and analysis, eager to explore ways library staff and researchers could put them to use?
+
+We value diversity of skills, voices, and lived experiences. We are committed to diversity and equal access within digital humanities, we encourage the participation of women, members of marginalised groups, LGBTQ+ community, and peoples from the Global South. All events in the **ENABLAR** project programme will take place online to maximise opportunities for participation. 
+
+## When is it happening?
+
+**Phase 1: Gather**
+- Call for participation open: 30 October 2025
+- Information webinar: 14 November 2025 
+- Call for participation close: 30 November 2025
+- Notifications sent to successful participants: 5 December 2025
+
+**Phase 2: Collaborate**
+- Orientation 1 (writing digital methods):  12 December 2025 (_indicative date_)
+- Orientation 2 (partnership building): 16 December 2025 (_indicative date_)
+- Lesson development workshops and asynchronous writing sprints:  January - March 2026
+
+**Phase 3: Publish**
+- Community Review Workshops:  April - May 2026
+- Draft **ENABLAR** submissions due: June 2026
+- Selection and support for publication: from July 2026
+
+## I’d like to get involved. What’s the next step?
+
+- If you’re interested in taking part, we encourage you to join our **information webinar** which will include an open question and answer session. After the session, we'll add a summary of questions asked and answers given to this blog post.
+  - The webinar will take place at [12:30 GMT](https://www.timeanddate.com/worldclock/converter.html?iso=20251114T123000&p1=tz_gmt) on **14 November 2025**. 
+  - Register to join: [tinyurl.com/enablar-info](https://tinyurl.com/enablar-info)
+
+- Complete our  short online **application** via Google Forms: [tinyurl.com/enablar-apply](https://tinyurl.com/enablar-apply). There's also a [plain text version of the form](/assets/forms/enablar-application-to-participate.txt) available, which you can complete and [email to our Publishing Manager](mailto:[email protected]) directly if you prefer. It provides space for you to tell us about yourself, your interest in the programme, and what you hope to achieve by participating.
+  - Applications close: **30 November 2025**
+  - We’ll write to you to let you know if your application has been successful.
+ 
+## Questions asked at our information webinar
+
+People who attended our information webinar on 14 November 2025 asked the following questions which might be useful to others:
+
+- **Question**: How is this different to the usual _Programming Historian_ lesson development process?  
+- **Answer**: ENABLAR is different to the usual lesson development process in several key ways. Firstly, those in the ENABLAR cohort will be supported to establish new, cross-disciplinary co-author partnerships. Secondly, through ENABLAR's programme of webinars, workshops, and writing sprints, the whole writing process will be facilitated. Thirdly, ENABLAR lessons will be guided to focus on methods, processes, and tools that build digital skills capacity among library and archives professionals.
+
+--
+
+- **Question**: What will the final output be?  
+- **Answer**: The final output will be a set of new co-authored article-length lessons which support computational processing, discovery, or analysis of digital library and archive collections. These lessons will combine instructive narrative with code that readers will be able to adapt for their own use case. While each ENABLAR co-author pair will be invited to submit their draft to _Programming Historian in English_ for consideration, only lessons selected for development by our editorial team will be guided through a formal open peer review process towards first publication in our English-language journal. Drafts not selected for the journal will be published as ‘grey literature’ outputs.
+
+--
+
+- **Question**: What level of technical skill are you hoping that participants/applicants will have?  
+- **Answer**: We're seeking a mixed cohort of people who are ready to learn from each other. ENABLAR will encourage knowledge exchange, and help build partnerships to advance all participants' knowledge and skills.
+
+--
+
+- **Question**: Does the possibility/impossibility to match participants through partnerships have an impact on the evaluation of applications?  
+- **Answer**: Yes, in the sense that we seek to bring together a cohort who represent a balance of perspectives across libraries and archives, and digital humanities research communities.
+
+--
+
+- **Question**: Is it possible to partner collaborators who are known to each other? (that is, could a librarian and a researcher apply jointly and work together?)  
+- **Answer**: Yes, it's possible. We advise you and your collaborator to apply separately, mentioning your idea for forming a co-author partnership. We still want to understand what interests you individually, and learn what each of you hope to achieve by participating in ENABLAR. We'd also like to be able to cultivate and explore some new collaborations!
+
+--
+
+- **Question**: The form is a Google Form that seems to require a sign in. How might individuals without (professional) Google accounts complete it?  
+- **Answer**: We've created a [plain text version of the form](/assets/forms/enablar-application-to-participate.txt), which you can complete and [email to our Publishing Manager](mailto:[email protected]) directly.
+
+--
+
+- **Question**: Is there any financial support available for time spent participating?  
+- **Answer**: No, participation would be voluntary. It will be important to ensure you have capacity within your schedule to participate without financial compensation. 
+
+--
+
+- **Question**: Will there be any need for travel?  
+- **Answer**: No, ENABLAR is an online-only programme to maximise opportunities for participation.

_posts/2025-11-14-en-call-for-proposals-2025-6.md

@@ -0,0 +1,80 @@
+---
+title: Call for Proposals (English edition)
+authors:
+- Alex Wermer-Colan
+- Laura Alice Chapot  
+- Anisa Hawes
+layout: post
+categories: posts
+---
+
+The [English edition of Programming Historian](/en/lessons/) seeks proposals for new original lessons or translations to be considered for publication in 2026.
+
+**Submissions Open**: 15 November 2025  
+**Submissions Close**: 15 February 2026
+
+## What is a _Programming Historian_ lesson?
+
+A _Programming Historian_ lesson is a learn-by-doing resource that empowers readers to develop new, practical knowledge of a computational method or digital tool. Our aim is for readers to be able to apply what they learn to acquire, transform, analyse, visualise, or sustain data in their own research.
+
+Successful lessons centre real datasets and sample code that readers can handle and experiment with. These elements are supported by reflections on methodological decision-making as well as considerations of adaptations to methods or alternative tool options – this is what makes a _Programming Historian_ lesson distinct from software documentation.
+
+Our lessons are aimed at humanities and social science researchers, but are also read by self-learners with other interests. We encourage our authors to write as though they are explaining their method to a colleague or peer, to make lessons as accessible as possible.
+
+## What are the benefits of writing a _Programming Historian_ lesson?
+
+Our lessons support readers who want to learn new skills, but the act of writing is also beneficial to authors. Writing to explain a methodology or tool to others deepens your own understanding and knowledge. It empowers your development as a critical, intentional and considered researcher, and is an opportunity to hone your technical writing skills. We encourage you to write about a method or tool and dataset that you know well, and that you have applied, adapted or advanced in your own research.
+
+## How to Submit a Proposal
+
+We've set up [a Google Form](https://tinyurl.com/ph-en-proposal-form-2025) which you can submit directly online. There's also [a plain-text version](/assets/forms/Lesson.Query.Form.txt) which you can [send to us by email](mailto:[email protected]), if you prefer. 
+
+There is space for you to tell us about the research use case you'd like to centre within your lesson, and for you to explain how you came to use this method or tool as part of your work within the humanities.
+
+Our questions encourage you to think carefully about how your choices of software, programming languages and datasets can support our commitment to openness.
+
+We will also ask you to outline any technical prerequisites and potential limitations of access to this method or tool because our global readership work with different operating systems and have varying computational resources.
+
+It is important to us that our lessons can be translated for use in multilingual research-contexts, so we'll ask you to consider how your method or tool could be applied or adapted for use with non-English-language data.
+
+If you're proposing a translation, the form provides an opportunity for you to think about how you could adapt or localise the research use case centred by the original lesson for an English-language readership. We'll also ask you to share a short translation sample. 
+
+At the end of the form, you are invited to provide links to sample code or to a rough draft of your lesson.
+
+
+## Ideas for Proposals
+
+_Programming Historian_'s English edition is inviting proposals to fill gaps in our lesson directory. Please explore [our journal](/en/lessons/) to discover what’s already available, and consider what you might be able to add. You can either:
+
+- Propose an original English-language lesson
+- Propose a translation into English of an existing, original [Spanish](/es/lecciones/), [French](/fr/lecons/), or [Portuguese](/pt/licoes/) lesson published in one of the other _Programming Historian_ editions. In this call, we would particularly like to encourage proposals **for translations of the following lessons**:
+
+**From Spanish**:  
+- [Reutilizar colecciones digitales: GLAM Labs](/es/lecciones/reutilizando-colecciones-digitales-glam-labs) 
+- [Uso de las colecciones del HathiTrust para el análisis de textos literarios en R](/es/lecciones/uso-las-colecciones-hathitrust-mineria-textual-R) 
+- [Introducción a ImagePlot y la visualización de metadatos de colecciones de imágenes](/es/lecciones/introduccion-a-imageplot-y-la-visualizacion-de-metadatos)
+
+**From French**:
+- [Préserver et rendre identifiables les logiciels de recherche avec Software Heritage](/fr/lecons/preserver-logiciels-recherche) 
+- [La reconnaissance automatique d'écriture à l'épreuve des langues peu dotées](/fr/lecons/transcription-automatisee-graphies-non-latines) 
+- [Introduction à Heurist](/fr/lecons/introduction-a-heurist) 
+
+**From Portuguese**:
+- [Investigar a literatura lusófona através dos tempos usando a Literateca](/pt/licoes/investigar-literatura-lusofona-literateca) 
+
+
+**If you have an idea, please send us a proposal by 15 February 2026.**
+
+Our editorial team will review all proposals, and return feedback **by 15 March 2026**. Proposals are considered on the basis of how well they serve the needs of the community, and whether they support our journal’s ambitions of openness, global access, multilingualism and sustainability. **Selected proposals will be invited for submission as first drafts within 45 days.**
+
+>In keeping with our commitment to diversity and equal access within digital humanities, we encourage proposals from women, members of marginalised groups, LGBTQ+ members, and peoples from the Global South. With this call, we strongly encourage the participation of Anglophone and multilingual communities beyond North America.
+
+## Questions
+
+If you’d like to ask any questions, please write to the Managing Editor of _Programming Historian_ in English, [Alex Wermer-Colan](mailto:[email protected]) or to our Publishing Manager, [Anisa Hawes](mailto:[email protected]).
+
+## Some background about _Programming Historian_
+
+Launched in 2012, _Programming Historian_ offers more than 250 novice-friendly, multilingual peer-reviewed lessons that help humanists learn a wide range of digital tools, techniques, and workflows to facilitate their research. In recent years, our interdisciplinary publication has expanded to include [Spanish](/es/lecciones/), [French](/fr/lecons/), and [Portuguese](/pt/licoes/) editions. Our journals are Diamond Open Access and in that spirit: authors retain copyright, never pay any fees to publish with us, all content is peer-reviewed, and access is always free for readers.
+
+We’re a volunteer-led initiative, supported by the Board of the charity ProgHist Ltd, a small team of publishing staff, and a global community of contributors. We’re funded by [a growing network of organisations](/en/supporters) across Europe, Canada, North America and Latin America who have invested in our success by subscribing to our [Institutional Partner Programme](/en/ipp).