From dd3e024eb39cb8435c496a99aac935a89ca9059f Mon Sep 17 00:00:00 2001
From: Anisa Hawes <87070441+anisa-hawes@users.noreply.github.com>
Date: Fri, 1 Dec 2023 18:41:54 +0000
Subject: [PATCH 1/3] Update contribute.md
Update line 19.
---
en/contribute.md | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/en/contribute.md b/en/contribute.md
index 9b772be717..53c2f1d2bd 100755
--- a/en/contribute.md
+++ b/en/contribute.md
@@ -16,8 +16,7 @@ Writing a tutorial is one of the best ways to teach yourself particular skills a
We don't simply accept or reject articles like traditional journals. Our editors collaborate with you to help craft your essay to be as clear and as useful as possible--a great way to improve your technical writing skills. Please read more about our [submission process]({{site.baseurl}}/en/author-guidelines).
-If you'd like to propose a lesson (for you or for someone else to write), [email the managing editor](mailto:english@programminghistorian.org).
-
+Our English journal is currently [inviting proposals](/posts/en-call-for-lessons) for new original lessons or translations to be considered for publication in 2024. If you have an idea, [please send us a proposal](https://tinyurl.com/ph-en-proposals) by January 12th, 2024.
## Edit lessons
From 705d19debd68bfce79665a5b53889ff06e34b082 Mon Sep 17 00:00:00 2001
From: Anisa Hawes <87070441+anisa-hawes@users.noreply.github.com>
Date: Fri, 1 Dec 2023 18:47:08 +0000
Subject: [PATCH 2/3] Update author-guidelines.md
Update Step 1: Proposing a New Lesson
---
en/author-guidelines.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/en/author-guidelines.md b/en/author-guidelines.md
index 37217c5dc0..03cd398a28 100755
--- a/en/author-guidelines.md
+++ b/en/author-guidelines.md
@@ -20,12 +20,13 @@ These guidelines have been developed to help you understand the process of creat
## Step 1: Proposing a New Lesson
-We welcome tutorials relevant to the humanities, pitched at any level of technical aptitude and experience, that focus on one problem or process, can be sustainable in the long term, and are addressed to a global audience.
+Our English journal is currently [inviting proposals](/posts/en-call-for-lessons) for new original lessons or translations to be considered for publication in 2024. If you have an idea, [please send us a proposal](https://tinyurl.com/ph-en-proposals) by January 12th, 2024.
+We are seeking lessons which are relevant to the humanities, pitched at any level of technical aptitude and experience, that focus on one problem or process, can be sustainable in the long term, and are addressed to a global audience.
The scope and length of the tutorial should be appropriate to the complexity of the task. Tutorials should not exceed 8,000 words (including code). Shorter lessons are welcome. Longer lessons may need to be split into multiple tutorials.
-If you have an idea for a new lesson, complete a lesson [proposal form](/assets/forms/Lesson.Query.Form.txt) and send it to [the managing editor](mailto:english@programminghistorian.org).
+**If you have an idea, please send us a proposal by January 12th, 2024**. We’ve set up [a Google Form](https://tinyurl.com/ph-en-proposals) 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:english@programminghistorian.org), if you prefer.
You can get a sense of what we publish by looking through our [published lessons]({{site.baseurl}}/en/lessons), reading our [reviewer guidelines]({{site.baseurl}}/en/reviewer-guidelines) or browsing [lessons in development](https://github.com/programminghistorian/ph-submissions/tree/gh-pages/en/drafts). Please also take a moment to check our [Lesson Concordance document](https://docs.google.com/spreadsheets/d/1vrvZTygZLfQRoQildD667Xcgzhf_reQC8Nq4OD-BRIA/edit#gid=0) to see which methods we have already covered in our published or forthcoming lessons.
From 8ffb0ace2ac5fd58377016d190a653710eaaa3e8 Mon Sep 17 00:00:00 2001
From: Anisa Hawes <87070441+anisa-hawes@users.noreply.github.com>
Date: Fri, 1 Dec 2023 19:09:14 +0000
Subject: [PATCH 3/3] Update author-guidelines.md
- Replace Markdown link syntax with html at line 23-4
- Adjust wording at line 27
---
en/author-guidelines.md | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/en/author-guidelines.md b/en/author-guidelines.md
index 03cd398a28..7aa9f9ddf4 100755
--- a/en/author-guidelines.md
+++ b/en/author-guidelines.md
@@ -20,13 +20,11 @@ These guidelines have been developed to help you understand the process of creat
## Step 1: Proposing a New Lesson
-Our English journal is currently [inviting proposals](/posts/en-call-for-lessons) for new original lessons or translations to be considered for publication in 2024. If you have an idea, [please send us a proposal](https://tinyurl.com/ph-en-proposals) by January 12th, 2024.
-We are seeking lessons which are relevant to the humanities, pitched at any level of technical aptitude and experience, that focus on one problem or process, can be sustainable in the long term, and are addressed to a global audience.
-
-The scope and length of the tutorial should be appropriate to the complexity of the task. Tutorials should not exceed 8,000 words (including code). Shorter lessons are welcome. Longer lessons may need to be split into multiple tutorials.
+Our English journal is currently
inviting proposals for new original lessons or translations to be considered for publication in 2024. If you have an idea,
please send us a proposal by January 12th, 2024.
+We are seeking proposals which are relevant to the humanities, pitched at any level of technical aptitude and experience, that focus on one problem or process, can be sustainable in the long term, and are addressed to a global audience.