INFRA: ci fix run on pr and main; CONTENT: fix peer review guide links throughout

INFRA: Build site on PR & fix links throughout

Author: lwasser

.github/workflows/build-site.yml

@@ -1,9 +1,10 @@
 name: Build and Jekyll site and run htmlproofer
 
 on:
+  pull_request:
   push:
     branches:
-      - '*'
+      - main
 
 jobs:
   github-pages:

_includes/archive-cards.html

@@ -2,7 +2,9 @@
 <!--  -->
 <div class="feature__item">
     <a href="{{ post.url}}">
+    {% if post.feature_img %}
     <img src="{{ post.feature_img }}" alt="{{ post.feature_alt }}">
+    {% endif %}
 <div class="card">
 
     <div class="archive__item">
@@ -16,5 +18,4 @@ <h3 class="card-title">{{ post.title | markdownify | strip_html | truncate: 60 }
 </a>
 </div>
 </div>
-<!--  -->
 

_pages/home.md

@@ -11,8 +11,8 @@ header:
     actions:
         - label: "Submit a Package"
           url: "https://github.com/pyOpenSci/software-review/issues"
-        - label: "Read our Handbook"
-          url: "/contributing-guide/intro"
+        - label: "Read our Peer Review Guide"
+          url: "https://www.pyopensci.org/peer-review-guide/"
 mission:
   - excerpt: 'We build diverse community that supports free and open Python tools for processing scientific data. We also build technical skills needed to contribute to open source and that support open science. Join our global community.'
 programs:
@@ -26,8 +26,8 @@ programs:
     alt: "placeholder image 2"
     title: "Open Peer Review"
     excerpt: "Our open peer review process of Python tools supports standardized software quality and usability. It also provides needed credit and visibility to tool maintainers. Finally it removes redundancy of packages with similar functionaly across the scientific Python ecosystem."
-    url: https://www.pyopensci.org/contributing-guide/open-source-software-peer-review/intro.html
-    btn_label: "Read More About Our Peer Review"
+    url: /python-packages/
+    btn_label: "Learn More About Package Peer Review"
     btn_class: "btn--primary"
   - image_path: images/brooke-cagle-unsplash.png
     title: "Skills for Open Source and Open Science"

_pages/python-packages.md

@@ -27,7 +27,7 @@ classes: wide
             <p>You're in the right place! Learn about the steps to submit a package
             for open peer review in our guidebook. </p>
           </div>  
-          <p><a href="https://www.pyopensci.org/contributing-guide/open-source-software-submissions/author-guide.html" class="btn btn--inverse"><i class="fas fa-angle-right"></i> View our Author Guide </a></p>
+          <p><a href="https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/author-guide.html" class="btn btn--inverse"><i class="fas fa-angle-right"></i> View our Author Guide </a></p>
       </div>
     </div>
   </div>
@@ -53,11 +53,11 @@ classes: wide
       <div class="archive__item-body">
           <h2 class="archive__item-title">See Our Review Process in Action</h2>
           <div class="archive__item-excerpt">
-            <p>Our reviewers happen in GitHub issues. This means that anyone can 
+            <p>Our reviews happen in GitHub issues. This means that anyone can 
             check in on any part of any review and read all of the conversation. 
             Check it out.</p>
           </div>  
-          <p><a href="" class="btn btn--inverse"><i class="fas fa-angle-right"></i> See Open Reviews </a></p>
+          <p><a href="https://github.com/pyOpenSci/software-review/issues" class="btn btn--inverse"><i class="fas fa-angle-right"></i> See Open Reviews </a></p>
       </div>
     </div>
   </div>

_pages/resources.md

@@ -1,22 +1,18 @@
 ---
 layout: single
-title: "More Resources"
+title: "pyOpenSci Resources"
 author_profile: false
 published: true
 site-map: true
 permalink: /resources/
 ---
 
-Here are some links to our resources and related sites:
+We are currently working on all of our organization-wide documentation and 
+governance. The guidebook links below are being updated and we welcome feedback!
 
 * [**pyOpenSci Github Organization**](https://github.com/pyOpenSci): Contains our [software-review](https://github.com/pyOpenSci/software-review) repo that hosts the peer-review process. Also contains our guidebook, cookiecutter, and governance repos (see below).
 
-* [**pyOpenSci Discourse Forum**](https://pyopensci.discourse.group/): Our community forum for discussing all things pyOpenSci. Have feedback or ideas about the review process? Need help finishing or maintaining your Python package? Have a question about how to use one of pyOpenSci’s packages? Our forum is the best place for these types of discussion.
+* [**pyOpenSci Peer Review**](https://www.pyopensci.org/peer-review-guide/): Contains information for package authors and reviewers.
 
-* [**pyOpenSci Guidebook**](https://www.pyopensci.org/contributing-guide/intro): Contains information for package authors and reviewers, including our [package guide](https://www.pyopensci.org/contributing-guide/authoring/index.html#packaging-guide), our [peer review process](https://www.pyopensci.org/contributing-guide/intro.html), and tips for [package maintenance](https://www.pyopensci.org/contributing-guide/open-source-software-peer-review/policies-and-guidelines.html#after-acceptance-package-ownership-and-maintenance). If you are interested in submitting a package to pyOpenSci, start with our [author guide](https://www.pyopensci.org/contributing-guide/authoring/index.html) and the links within it.
+* [**pyOpenSci's Governance**](https://www.pyopensci.org/governance/): Where we discuss the direction and scope of pyOpenSci. We're a community organization, so please feel free to create an [issue](https://github.com/pyOpenSci/governance/issues) if you have any questions or concerns!
 
-* [**pyOpenSci's Governance Repo**](https://github.com/pyOpenSci/governance): Where we discuss the direction and scope of pyOpenSci. We're a community organization, so please feel free to create an [issue](https://github.com/pyOpenSci/governance/issues) if you have any questions or concerns!
-
-* [**pyOpenSci cookiecutter**](https://cookiecutter-pyopensci.readthedocs.io/en/latest/): We created a cookiecutter template to make packaging your python code easier. The cookiecutter follows all our guidelines from our [packaging guide](https://www.pyopensci.org/contributing-guide/authoring/index.html#packaging-guide).
-
-* [**rOpenSci**](https://ropensci.org/): We draw inspiration from rOpenSci, a community to help promote, teach, and grow best-practices in software development for the Scientific R stack. They have a wonderful array of resources for R, such as their [collection of scientific R packages](https://ropensci.org/packages/). If you use R, we encourage you to get involved with them.

_posts/2019-11-18-pandera-dataframe-validation.md

@@ -14,6 +14,7 @@ categories:
   - data-validation
   - dataframes
   - highlight
+comments: true
 ---
 
 Modern data engineering and analysis workflows will often involve using data

_posts/2020-04-29-movingpandas-movement-data-analysis.md

@@ -12,6 +12,7 @@ categories:
   - blog-post
   - pandas
   - spatial
+comments: true
 ---
 
 Movement data is everywhere: from tracking apps that record human or vehicle movement to ecologists monitoring wildlife behavior. Movement data analysis is challenging since movement data combines time series and spatial data analyses questions. Existing spatial analysis libraries, such as GeoPandas, are great at handling spatial data but they don't support moving objects. 

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

@@ -101,7 +101,7 @@ There are a few ways to get involved with us now.
 1. [You can sign up to be a reviewer by filling out our reviewer form](https://forms.gle/B6zAukLCvJot5nws6). If you do this, we will reach out to you if a package is submitted that suits your background and interests!
   * We will also be growing our editorial board in the upcoming months. Once you have reviewed for us you are eligible to be considered as an editor. We will be posting more about this process in the upcoming months.
 1. Our open peer review process is running! If you have a package that you are working on, [you can submit it to our peer review process](https://github.com/pyOpenSci/software-review/issues). 
-  * You can learn more about our review process here in our [community guide (which will be updated in the upcoming months so that it is more clear)](https://www.pyopensci.org/contributing-guide/open-source-software-peer-review/aims-and-scope.html).
+  * You can learn more about our review process here in our [community guide (which will be updated in the upcoming months so that it is more clear)](https://www.pyopensci.org/peer-review-guide/about-peer-review/aims-and-scope.html).
   * If you have a package that you wish to submit but need some guidance, you can also submit a presubmission inquiry or a request for help here.
 2. You can [follow us on twitter](https://www.twitter.com/pyopensci) to keep tabs on our progress. 
 

_posts/2022-09-27-call-for-python-software-review-editors.md

@@ -12,12 +12,13 @@ categories:
   - blog-post
   - highlight
   - peer-review
+comments: true
 ---
 
 ## An update on pyOpenSci's review process 
 
 Hey there! I just wanted to update everyone about where pyOpenSci is with 
-its peer review process. We are currently hard at work updating [our guides](https://www.pyopensci.org/contributing-guide/intro.html) to 
+its peer review process. We are currently hard at work updating [our peer review guides](https://www.pyopensci.org/peer-review-guide/) to 
 streamline the peer review process. For the next 2 months (October & November 2022) 
 we will prioritize setting up an editorial board to support new reviews as they 
 come in. 
@@ -28,7 +29,7 @@ With that below you will find a few updates.
 
 [David Nicholson](https://github.com/NickleDave), who has been working with pyOpenSci for the past few years as 
 an editor will take on the Editor in Chief role! [You can learn more about that 
-role here](https://www.pyopensci.org/contributing-guide/open-source-software-submissions/editor-in-chief-guide.html) in our peer review guide. This position will rotate once we have our editorial board setup.
+role here](https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/editor-in-chief-guide.html) in our peer review guide. This position will rotate once we have our editorial board setup.
 
 As Editor in Chief, David will:
 
@@ -57,7 +58,7 @@ longer given mutual consent. You will be responsible for handling 3-4 package
 reviews during that year. We may also bring on guest editors in other 
 instances, e.g., because of their familiarity with a specific domain.
 
-You can read more about the [roles and responsibilities of and editor here](https://www.pyopensci.org/contributing-guide/open-source-software-submissions/editors-guide.html). 
+You can read more about the [roles and responsibilities of and editor here](https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/editors-guide.html). 
 
 We currently have a package in the queue that is spatial / remote sensing related
 that we'd love to have an editor onboard to review. But we are in need of editors

_posts/2022-10-24-why-should-python-open-source-matter-science.md

@@ -13,6 +13,7 @@ categories:
   - python-packaging
   - peer-review
 toc: false
+comments: true
 ---
 
 ## Why Python open source package health should matter to you as a scientist 
@@ -192,7 +193,7 @@ So how do we track open source tool health (for science)?
 
 ### Peer review is actually the second step in our process. 
 
-We won't begin to review a package [without bare minimum checks](https://www.pyopensci.org/contributing-guide/open-source-software-submissions/author-guide.html#pyopensci-review-guide-for-python-open-source-package-authors).
+We won't begin to review a package [without bare minimum checks](https://www.pyopensci.org/peer-review-guide/software-peer-review-guide/author-guide.html#does-your-package-meet-packaging-requirements).
 We hope that these bare minimal checks help maintainers as they try to decide
 what is good enough infrastructure for their package.