-
I don't think we've ever compiled a list of what needs to happen when we bring a new member of the team on board. I thought I'd try to do that so we can smooth the transition in future. Please add ite…
-
*The Programming Historian en español* ha recibido la siguiente propuesta de traducción *Editar con Audacity* de la lección [Editing with Audacity](https://programminghistorian.org/lessons/editing-aud…
-
As noted by @acrymble here https://github.com/programminghistorian/jekyll/issues/684, at the moment in the spanish version of the [team page](https://programminghistorian.org/es/equipo-de-proyecto) th…
-
The Programming Historian has received a proposal for a lesson on Digital Preservation.
-
Rule 3 has a paragraph on the Programming Historian omnibus person, so I thought it would make sense to add a brief mention of the SWC/DC code of conduct.
-
Reviving an old idea (see https://github.com/programminghistorian/jekyll/issues/531 and https://github.com/programminghistorian/jekyll/issues/417). Potential benefits:
- Creates a digital object wi…
-
Our content is part of the Directory of Open Access Journals (DOAJ), which makes it easier for libraries to add it to their catalogue. This was set up in Issue #180 a couple of years ago. Lesson metad…
-
Issue to flag a conversation for our Editorial Meeting agenda.
With the change over in editors and with an increase in lesson proposals, it seems time to have a conversation as an Editorial team ab…
-
The [Digital Humanities Network](https://www.humanities.utoronto.ca/DH_at_UofT) and Jackman Humanities Institute in collaboration with UofT Coders will be holding a two-day workshop on **Dec 11 and 12…
-
The Programming Historian has received the following tutorial on 'Geoparsing Text with the Edinburgh Geoparser' by @bea-alex. This lesson is now under review and can be read at:
http://programminghis…