User flow links

Author: lwasser

_pages/partners.md

@@ -13,6 +13,9 @@ scientists:
     alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
     excerpt: "Our catalog of vetted open source tools makes it easier for scientists to find the trusted tools that they need to develop their open science workflows."
     title: "Help scientists find the open science tools that they need"
+    url: https://www.pyopensci.org/python-packages.html
+    btn_label: View our growing list of accepted scientific Python packages
+    btn_class: btn--primary
 mission:
   - excerpt: "Domain-specific communities can partner with PyOpenSci to leverage both our peer review process and development of Python packaging packaging guidelines."
 packaging-easier:
@@ -21,30 +24,49 @@ packaging-easier:
      title: "Let's make packaging easier for scientists, together"
      excerpt: "Given the numerous diverse packaging options, many communities are crafting their own guidelines and review processes. Partnering with pyOpenSci enables your community to:
 
-     * tap into and contribute to an established community-owned set of packaging standards.
+     * tap into and contribute to an established community-owned set of packaging guidelines.
 
      * mitigate the redundancy of multiple communities creating their own processes and standards.
 
 
      Aligning packaging criteria supports increased consistency in packaging approaches across the Python ecosystem. This consistency will  lower the barrier of entry for new potential contributors."
+     url: https://www.pyopensci.org/python-package-guide.html
+     btn_label: View our Python packaging guide
+     btn_class: btn--primary
 
 community:
    - image_path: images/pyopensci-women-collaborating.png
      alt: "A black and white pencil sketch of a group of 5 women sitting and standing around a laptop working together."
-     excerpt: "
-pyOpenSci is driven by a **vibrant community** of technical packaging experts, open science enthusiasts, and Pythonistas. When you partner with pyOpenSci, you:
+     excerpt: "pyOpenSci is driven by a **vibrant community** of technical packaging experts, open science enthusiasts, and Pythonistas. When you partner with pyOpenSci, you:
 
-* become part of a community rich in expertise, ready to assist you with your packaging challenges.
+    * Become part of a community rich in expertise, ready to assist you with your packaging challenges.
 
-* As a package grows, we help your community maintainers decide what to do if they need to step down from maintenance roles, be it finding a new maintainer or gracefully archiving the package for safekeeping."
+    * As a package grows, we help your community maintainers decide what to do if they need to step down from maintenance roles, be it finding a new maintainer or gracefully archiving the package for safekeeping."
      title: "Harness the power of community"
+     url: https://www.pyopensci.org/our-community/index.html
+     btn_label: Explore our community contributors
+     btn_class: btn--primary
+leverage:
+   - title: "Leverage our peer review process"
+     excerpt: "Your community can take advantage of our existing, developed and well-documented peer review process which includes:
 
+     * **A diverse and growing team of editors.** We ask partner communities to have at least 2 members of their community on our editorial team. We want our partner community to make the final decision on whether a package should receive the label of being affiliated. Typically an editor will run 2-4 reviews a year. [Learn more about the editor role.](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html)
+
+     * **A suite of community reviewers whose expertise spans numerous scientific domains.** We ask that partner communities help us find reviews in their specific domain areas as packages come in for review. [Learn more about the requirements for reviewers.](https://www.pyopensci.org/software-peer-review/how-to/reviewer-guide.html)
+
+     * **Community driven packaging resources and guidelines:** Our packaging guidelines drive the peer review process. Instead of communities creating their own individual guidelines, pyOpenSci partners collaborate with us to expand packaging resources."
+     url: https://www.pyopensci.org/python-packages.html
+     btn_label: View our growing list of accepted scientific Python packages
+     btn_class: btn--primary
 partnerships:
   - image_path: /images/peer-review/peer-review-partners-process.png
     alt: "diagram with a set of 3 boxes with arrows pointing to the right. The first box says submit your package with a code icon above it. The second says Review with pyOpensci Standards below. Blow the second box is a dark purple box that says Your community standards in it. And an arrow pointing to that box that says customized review. The third box says Accepted pyos + community affiliated."
     excerpt: "
-pyOpenSci adds an extra layer of community-specific review to our established open peer review process. This allows domain-specific scientific Python communities to vet affiliated tools through our robust peer review process. Communities then don't have to develop and maintain their own review processes and software guidelines."
+pyOpenSci adds an [extra layer of community-specific review](https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html) to our established open peer review process. This allows domain-specific scientific Python communities to vet affiliated tools through our robust peer review process. Communities then don't have to develop and maintain their own review processes and software guidelines."
     title: "Community Partnerships Streamline Peer Review & Packaging Standards"
+    url: https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html
+    btn_label: Learn more about how community partnerships work.
+    btn_class: btn--primary
 partnership_benefits:
   - image_path: /images/peer-review/pyos-partnerships-peer-review.png
     alt: "Diagram with a light purple background. On the left there is the pyOpenSci purple flower and it says accepted with a check mark above. There are two arrows leading to boxes on the right. The top box says JOSS published with a check next to it and the JOSS logo. The box below says Community Affiliated with a check. THe boxes are numbered 1,2,3. "
@@ -102,15 +124,10 @@ We will:
 {% include div_purple_bottom.html  %}
 
 <div class="pyos-section" markdown="1">
-
 <div class="content" markdown="1">
-## Leverage our peer review process
 
-Your community can take advantage of our existing, developed and well-documented peer review process which includes:
+{% include feature_row id="leverage" type="right" %}
 
-- **A diverse and growing team of editors.** We ask partner communities to have at least 2 members of their community on our editorial team. We want our partner community to make the final decision on whether a package should receive the label of being "affiliated". Typically an editor will run 2-4 reviews a year. [Learn more about the editor role.](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html)
-- **A suite of community reviewers whose expertise spans numerous scientific domains.** We ask that partner communities help us find reviews in their specific domain areas as packages come in for review. [Learn more about the requirements for reviewers.](https://www.pyopensci.org/software-peer-review/how-to/reviewer-guide.html)
-- **Community driven packaging resources and guidelines:** Our packaging guidelines drive the peer review process. Instead of communities creating their own individual guidelines, pyOpenSci partners collaborate with us to expand packaging resources.
 </div>
 </div>