feat(blog): add event page for packaging course (#820)

* feat(blog): add event page for packaging course

* fix: update footers to remove broken discourse link

Author: lwasser

_data/navigation.yml

@@ -39,15 +39,10 @@ main:
         url: "/blog/index.html"
       - title: Events
         url: "/events.html"
-      - title: Ask a question
-        url: "https://pyopensci.discourse.group/"
-        icon: "fa-brands fa-discourse"
   - title: "Community"
     sub-nav:
       - title: "Our Community"
         url: "/our-community/index.html"
-      - title: "Connect with us"
-        url: "https://pyopensci.discourse.group/"
         icon: "fa-brands fa-discourse"
       - title: "Handbook"
         icon: "fas fa-external-link-alt"
@@ -57,5 +52,5 @@ main:
       - title: "Volunteer"
         url: "/volunteer.html"
   - title: "Donate"
-    url: "https://fnd.us/pyopensci_2024"
+    url: "https://give.communityin.org/pyopensci_2024"
     is_button: true

_includes/event_instructors.html

@@ -0,0 +1,36 @@
+{% if page.instructors %}
+<div class="event-instructors">
+  <div class="grid event-instructors__grid">
+    {% for person in page.instructors %}
+    <div class="cards people-card event-instructor">
+      <div class="people-card__content">
+        <div class="person_img event-instructor__avatar">
+          <img
+            src="https://github.com/{{ person.github }}.png"
+            alt="GitHub profile photo of {{ person.name }}"
+            width="400"
+            height="400"
+            loading="lazy"
+          >
+        </div>
+        <div class="event-instructor__text">
+          <h4 class="person_name">
+            <a href="https://github.com/{{ person.github }}" rel="noopener noreferrer">
+              {{ person.name }}
+            </a>
+            <a
+              href="https://github.com/{{ person.github }}"
+              class="event-instructor__github-link"
+              rel="noopener noreferrer"
+              aria-label="{{ person.name }} on GitHub"
+            >
+            </a>
+          </h4>
+          <p class="event-instructor__bio">{{ person.bio | strip_newlines | strip }}</p>
+        </div>
+      </div>
+    </div>
+    {% endfor %}
+  </div>
+</div>
+{% endif %}

_pages/get-in-touch.md

@@ -11,16 +11,9 @@ redirect_from:
   - /get-involved-contact/
 get-involved:
   - image_path:
-    title: "Got a Packaging Question?"
+    title: "Submit a Python Package for Peer Review"
     alt:
-    excerpt: "If you are a scientist and have a question about packaging, our discourse forum is the place for you. We have volunteers from the pip and conda / conda-forge packaging ecosystem that can help you find the answers that you need. You can also ask questions about peer review there."
-    url: https://pyopensci.discourse.group/
-    btn_label: "> Ask a packaging question now"
-    btn_class: btn--inverse
-  - image_path:
-    title: "Submit a Scientific Python Package for Review"
-    alt:
-    excerpt: "Are you developing or maintaining a scientific Python package that is in scope for our peer review process? If so, consider submitting it for peer review. We partner with JOSS so you can submit to us and JOSS will accept our review as theirs. They then just review your paper. It's a win/win! Check out our [author guide](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html) to learn more about the process. Pro-tip: If you still aren't sure if your package is in scope for us, you can submit a pre-submission inquiry."
+    excerpt: "Are you developing or maintaining research software or a scientific Python package that is in scope for our peer review process? If so, consider submitting it for peer review. We partner with JOSS so you can submit to us and JOSS will accept our review as theirs. They then just review your paper. It's a win/win! Check out our [author guide](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html) to learn more about the process. Pro-tip: If you still aren't sure if your package is in scope for us, you can submit a pre-submission inquiry."
     url: https://github.com/pyOpenSci/software-submission
     btn_label: "> Submit a package now."
     btn_class: btn--inverse

_pages/learn.md

@@ -32,8 +32,7 @@ whats_next:
     alt: "A graphic with a light yellow background that says essential collaboration skills for scientists - using GitHub. On the right there is a man and a woman sitting at a tall table with laptops working."
     excerpt: "Through the [Better Software for Science Fellowship](https://bssw.io/pages/bssw-fellowship-program) we will be developing lessons focused on teaching core GitHub collaboration skills needed for both contributing to open source software and for working in an open science team environment.
 
-
-    **Stay up to date with course development and announcements in [our Discourse community](https://pyopensci.discourse.group/), as well as on [Fosstodon](https://fosstodon.org/@pyOpenSci) and [LinkedIn](https://www.linkedin.com/company/pyopensci/)**"
+    **Stay up to date with course development and announcements on [Fosstodon](https://fosstodon.org/@pyOpenSci) and [LinkedIn](https://www.linkedin.com/company/pyopensci/)**"
     title: "What's next: Collaborative GitHub for Scientists"
 toc: false
 ---

_pages/volunteer.md

@@ -17,8 +17,6 @@ build-skills:
 
 - **Learn new skills:** you don’t have to be a Python expert to get involved with pyOpenSci. We can help you level up your packaging game and learn how to constructively review both code and copy through contributions to our online learning resources.
 
-- **Meet and connect with new peers.** Our [public Discourse forum](https://pyopensci.discourse.group/) is a great place to ask and answer questions, as well as discuss packaging and open science with other Pythonistas.
-
 - **Get recognized** on the [pyOpenSci website](https://www.pyopensci.org/our-community/index.html) and in our [GitHub repositories](https://github.com/pyOpenSci): your contribution matters, and we want to ensure your work is recognized and celebrated in a public forum. If you serve as an editor you can also connect with pyOpenSci professionally as a volunteer for our organization on LinkedIn"
     image_path: /images/people-building-blocks.jpg
 diverse-backgrounds:

_posts/2022-09-10-executive-director-pyopensci-leah-wasser-updates.md

@@ -90,9 +90,7 @@ value support from some of you along the way!
 
 ## Stay in touch!
 Once I have a road map for activities developed, I will communicate this here on our
-[website](https://www.pyopensci.org/), [on Twitter](https://www.twitter.com/pyopensci)
-and [on discourse](https://pyopensci.discourse.group/). So be sure to
-follow us on Twitter and sign up for Discourse!
+[website](https://www.pyopensci.org/).
 
 ## What can you do now?
 There are a few ways to get involved with us now.

_posts/2023-03-22-demystifying-python-packaging.md

@@ -186,11 +186,3 @@ In the next few blog posts i'm going to present each Python build workflow tool
 - Poetry.
 
 I'll break down the pros and cons of using each tool. I will also provide examples of what using the tool looks like. In the meantime, [check out our shiny new packaging chapter here to see the overview of packaging tools and approaches for scientists creating pure Python packages](https://www.pyopensci.org/python-package-guide/package-structure-code/intro.html).
-
-## Tutorials are also on the way
-
-In the very near future i'll also create some packaging tutorials that will help you get started with creating a new package. Stay tuned for more on that as well!
-
-## Got questions on Python packaging?
-
-If you are just getting started with Python packaging OR if you have questions about it, please use our [discourse forum](https://pyopensci.discourse.group/) to ask questions. We are happy to help!

_posts/2023-09-11-community-manager-job-available.md

@@ -153,7 +153,7 @@ All work that you do should exemplify our community [Code of Conduct](https://ww
 - Growing our social media following and support community meetings and events
 - Working with the community to develop new blog posts on packages in our ecosystem
 - Developing and contributing to a mentorship program to support new contributors to open source
-- Curating and contributing content to our online community on [social media](https://fosstodon.org/@pyOpenSci), Slack, [Discourse](https://pyopensci.discourse.group/) and other platforms as needed.
+- Curating and contributing content to our online community on [social media](https://fosstodon.org/@pyOpenSci), Slack and other platforms as needed.
 
 ### Within 6 months, you will be…
 

_posts/2023-10-18-rse-2023-pyopensci-bof.md

@@ -217,7 +217,6 @@ My key takeaways from the US-RSE meeting is:
 
 - you can [review a pull request](https://github.com/pyOpenSci/python-package-guide/pulls) on our packaging guide. Or open and issue if you have a problem with the guide.
 - You can [sign up to be a reviewer for pyOpenSci here](https://docs.google.com/forms/d/e/1FAIpQLSeVf-L_1-jYeO84OvEE8UemEoCmIiD5ddP_aO8S90vb7srADQ/viewform)
-- You can post a packaging question in our [pyOpenSci Discourse forum here.](https://pyopensci.discourse.group/)
 
 As for me, I hope to attend the 2024 RSE meeting and to continue this important
 conversation around Python packaging and peer review of software.

_posts/2024-04-16-pyos-open-education-resources-announcement.md

@@ -73,7 +73,7 @@ All of our written content is available on the [Learn section of our website](ht
 
 Our vision for our free, online trainings is for the curriculum to be added to our library of open education resources, making them free, accessible, and published for anyone to use. And we intend to experiment with delivering this curriculum in an asynchronous, cohort-based manner that allows learners from all over the world to come together for a period of time to work through the curriculum together. If you were part of one of the original cohorts of the <a href="https://dslc.io/">R for Data Science Online Learning Community</a> created by our Community Manager, [Jesse Mostipak](https://github.com/kierisi), then you know that these asynchronous trainings will be thoughtfully crafted, a fantastic learning experience, and a ton of fun!
 
-pyOpenSci is the recipient of the [Better Software for Science Fellowship](https://bssw.io/fellows/leah-wasser), which will help fund the creation of these open educational resources. You can stay up to date with more information on these types of lessons through [our Discourse forum](https://pyopensci.discourse.group/) as well as [our mailing list](https://eepurl.com/iM7SOM).
+pyOpenSci is the recipient of the [Better Software for Science Fellowship](https://bssw.io/fellows/leah-wasser), which will help fund the creation of these open educational resources.
 
 These asynchronous trainings will be free, online, and center around community building and collaborative learning with larger cohort sizes. Part of the intention of these trainings is to foster a vibrant learning community where participants are empowered to learn from one another.
 
@@ -101,4 +101,4 @@ She will also briefly discuss how LLM’s can be used to support tasks such as d
 The course will take place on Thursday, April 25th, from 10AM–1PM Mountain time, and use the Spatial Chat platform. Tickets are $10, and can be purchased on [the workshop’s Eventbrite page](https://www.eventbrite.com/e/from-python-code-to-module-tickets-879586546037?aff=oddtdtcreator). The class size is capped at 35, and tickets are selling fast–we hope to see you there!
 
 ## Connect with us!
-You can stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci), and you can connect with the broader pyOpenSci community on [our Discourse forum](https://pyopensci.discourse.group/). And if you’re interested in our weekly newsletter where we share news, blog posts, and monthly updates, [subscribe on LinkedIn](https://www.linkedin.com/newsletters/pyopensci-newsletter-7179551305344933888!)
+You can stay up-to-date with all things pyOpenSci by following us on [LinkedIn](https://www.linkedin.com/company/pyopensci) and [Fosstodon](https://fosstodon.org/@pyOpenSci).