-
This ticket will host peer review comments for @shawngraham's tutorial ["Algorithmic Listening, (or, a gentle introduction to the sonification of historical data)".](http://programminghistorian.github…
-
It could be useful to build on [Hypothesis web annotation](http://hypothes.is) as a path for anyone working through a PH tutorial to leave inline suggestions for improvement, questions, "this is where…
-
As mentioned in issue #277, there is no clear way to get support or report bugs for Lexos. Perhaps we should add a link to the GitHub issues page (such links should also be added on the Lexomics and _…
-
This essay would be much more accessible and engaging with photographs showing the monuments and related individuals but I still need to figure out the best way of adding images with Markdown. Here is…
-
In keeping with our attempts to promote diversity and a safe place to share ideas, I wondered if we might not want to adopt an anti-harassment policy for reviewers, authors, and contributors to our fo…
-
Hi folks,
I keep getting errors that the build failed, and a cryptic email from github saying that markdown has to be changed to kramdown. I checked your _config.yml per that email, and found:
```
n…
-
this is relatively easy to do (if a bit time consuming; but could be divided up among many people), and could be a big help in helping new visitors understand the variety of lessons we have. if such a…
-
In allen Testdokumenten habe ich für `citeauthorformat=firstfull` keinen Fehler entdeckt;
dafür jetzt jedoch in meiner Dissertation.
Als Fehlermeldung erhalte ich:
```
! Extra \else.
\@include ...ed…
-
This is an open conversation for the whole world. Please feel free to contribute no matter who you are.
The Programming Historian has currently published contributions from 28 authors and has contrib…
-
Google scholar seems to struggle to get our tutorials right. They can't make out the authors from the reviewers, and don't get the difference between the whole site and individual tutorials. We might …