Merge pull request #3105 from programminghistorian/Issue-3104

Issue 3104
programminghistorian · Dec 1, 2023 · ca61835 · ca61835
2 parents 46d9783 + 8ffb0ac
commit ca61835
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 6 deletions.
diff --git a/en/author-guidelines.md b/en/author-guidelines.md
@@ -20,12 +20,11 @@ These guidelines have been developed to help you understand the process of creat
 ## Step 1: Proposing a New Lesson
 
 <div class="alert alert-success">
-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.
-
-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 <a href='/posts/en-call-for-lessons'>inviting proposals</a> for new original lessons or translations to be considered for publication in 2024. If you have an idea, <a href='https://tinyurl.com/ph-en-proposals'>please send us a proposal</a> 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.
 </div>
 
-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:[email protected]).
+**If you have an idea for a lesson, 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:[email protected]), 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. 
 

diff --git 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:[email protected]).
-
+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