Accessibily check

Author: lwasser

_includes/package-grid.html

@@ -1,8 +1,8 @@
 <div class="element-item cards bubble {% for aCategory in apackage.categories %}
 {{ aCategory }}
 {% endfor %}" data-category="data">
-    <article class="archive__item" itemscope itemtype="https://schema.org/CreativeWork">
-        <h3 class="card__title no_toc" itemprop="headline">
+    <article itemscope itemtype="https://schema.org/SoftwareApplication">
+        <h3 class="card__title no_toc" itemprop="name">
             {{ apackage.package_name }}
         </h3>
         <p class="page__meta contributors">

_pages/about-peer-review.md

@@ -1,25 +1,25 @@
 ---
 layout: splash
 permalink: /about-peer-review/
-title: "pyOpenSci Reviews Scientific Python Software"
+title: "pyOpenSci Makes Python Software Better and Easier to Find Through Peer Review"
 header:
   overlay_image: images/header.png
   overlay_filter: 0.8
 intro:
-  - excerpt: "Our open peer review process facilitates scientists getting credit and recognition for the work they've invested in developing scientific Python tools. The peer review process also supports scientists in finding vetted and maintained software, which drives their open science workflows."
+  - excerpt: "Our open peer review process makes scientific software better and easier to discover. [Check out our accepted packages.](https://www.pyopensci.org/python-packages.html)"
 benefits_scientists:
   - image_path: images/trusted-scientific-python-tools.png
     alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
     excerpt: "Through our partnerships with domain specific communities our catalog of trusted tools for scientists across domains continues to grow."
-    title: "Scientists need trusted and vetted tools to support their open science workflows."
+    title: "Scientists need trusted and vetted software"
     url: /partners.html
     btn_label: Learn more about scientific Python community partnerships
     btn_class: btn--primary
 benefits_maintainers:
   - image_path: images/pyopensci-supports-maintainers.png
     alt: "A pencil sketch of a round table with people sitting around it from different backgrounds working on laptops and also writing together."
     excerpt: "The pyOpenSci peer review process multiplies shared knowledge, making it easier for Pythonistas of all levels to accomplish challenging tasks, such as navigating the Python packaging ecosystem, with relative ease. And our diverse community supports scientific package maintainers in their efforts to develop and build robust software."
-    title: "pyOS software peer review benefits open source maintainers"
+    title: "Peer review benefits open source maintainers"
     url: https://www.pyopensci.org/software-peer-review/about/benefits.html
     btn_label: Learn more about the benefits of peer review
     btn_class: btn--primary
@@ -29,14 +29,14 @@ peer_review:
     excerpt: "Software peer review, similar to the review of scientific papers, is a process where scientists vet software code, documentation and infrastructure. pyOpenSci leads an [open peer review process](https://www.pyopensci.org/software-peer-review/our-process/how-review-works.html) run by a community of dedicated volunteers. Reviews are supportive and fully transparent with the shared goal of improving the quality, usability and maintainability of the software that is driving open science.
 
     * Diverse teams lead each review, enhancing the overall feedback quality."
-    title: "About peer review of scientific Python software"
+    title: "How Python software peer review works"
     url: https://www.pyopensci.org/software-peer-review/our-process/review-timeline.html
     btn_label: Learn more about the peer review timeline and roles
     btn_class: btn--primary
   - image_path: images/pyopensci-joss-partnership.png
     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 partnership with JOSS means that you don't have to choose between pyOpenSci and JOSS. Simply submit your package to pyOS for review. If your package is accepted and in scope for JOSS, it will be fast-tracked through JOSS' review process. "
-    title: "Get published with JOSS through a pyOpenSci review"
+    title: "Get a fast-track JOSS publication"
     url: https://www.pyopensci.org/software-peer-review/partners/joss.html
     btn_label: Learn more about our JOSS partnership
     btn_class: btn--primary
@@ -96,7 +96,7 @@ classes: flowing
 <div class="pyos-section purple">
 <div class="content" markdown="1">
 
-## Get involved with peer review
+## Get involved with software peer review
 
 {% include feature_row_pyos id="get-involved" %}
 
@@ -153,7 +153,7 @@ We are deeply grateful for those served on our editorial board previously!
 
 <div class="content">
 <div class="feature__wrapper">
-<h2> Recently Accepted scientific Python Packages</h2>
+<h2> Recently accepted Python packages</h2>
 
 {% assign packages_sorted = site.data.packages | sort_natural: 'date_accepted' | reverse %}
 

_pages/packaging-resources.md

@@ -3,7 +3,7 @@ layout: splash
 classes: flowing
 permalink: /python-packaging-science.html
 title: "Python packaging resources for scientists"
-excerpt: "We make the scientific Python package ecosystem easier to navigate through peer review and packaging resources."
+excerpt: "We make the Python package ecosystem easier to navigate through peer review and packaging resources."
 header:
   overlay_image: images/header.png
   overlay_filter: 0.8
@@ -12,15 +12,15 @@ intro:
 peer-review:
   - image_path: images/pyopensci-people-at-computer.jpg
     alt: "A pencil sketch of a round table with people from different backgrounds sitting around it, working on laptops and also writing together."
-    excerpt: "We run an open peer review process for scientific Python software. Peer review helps maintainers improve the quality, usability and long-term maintainability of scientific software."
-    title: Raising the bar for scientific Python software"
+    excerpt: "We run an open peer review process for Python software. Peer review helps maintainers improve the quality, usability and long-term maintainability of scientific software."
+    title: Raising the bar for Python software"
     url: https://www.pyopensci.org/about-peer-review/index.html
     btn_label: Learn more and get involved with peer review today.
     btn_class: btn--primary
 packaging-easier:
    - image_path: images/pyopensci-working-together.png
      alt: "A black and grey sketch of a group of people sitting at a desk in front of a monitor smiling."
-     title: "Get Involved: Help us improve our scientific Python packaging resources"
+     title: "Get Involved: Help us improve our  Python packaging resources"
      excerpt: "
      We need your help! Our packaging content is community-created and reviewed through an open review process on GitHub. The more feedback that we get, the more useful our resources are to the community. Get involved by:
 
@@ -64,7 +64,7 @@ toc: false
 {% include feature_row id="community-created" type="right" %}
 
 <div class="subsection" markdown="1">
-### Scientific Python packaging guidebook sections
+### pyOpenSci Python packaging guidebook sections
 
 <div class="tutorial__container">
 {% for atutorial in site.packaging %}

_pages/partners.md

@@ -14,7 +14,7 @@ scientists:
     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_label: Explore our accepted 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."
@@ -46,18 +46,6 @@ 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."
@@ -126,7 +114,20 @@ We will:
 <div class="pyos-section" markdown="1">
 <div class="content" markdown="1">
 
-{% include feature_row id="leverage" type="right" %}
+<!-- {% include feature_row id="leverage" type="right" %} -->
+
+## Leverage our peer review process
+
+Your science domain-specific community can take advantage of our existing, developed and well-documented peer review process which includes:
+
+* **A growing team of editors from a diverse set of scientific and technical backgrounds.** 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)
+
+* **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."
+
+[Learn more about our partnerships](https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html){: .btn  .btn--primary }
+
 
 </div>
 </div>
@@ -151,7 +152,8 @@ We will:
 
 <div class="pyos-section" markdown="1">
 <div class="content" markdown="1">
-## Raising the bar for Scientific Python software
+
+## Raising the bar for scientists developing Python software
 
 More packages going through our review process means
 we're all working together to raise the bar in terms of
@@ -164,7 +166,7 @@ By reviewing packages from the entire ecosystem, pyOpenSci can identify redundan
 
 <div class="pyos-section purple" markdown="1">
 <div class="content" markdown="1">
-## Why do so many scientific Python communities exist?
+## Why do so many domain specific Python communities exist?
 
 Within the Python ecosystem, various science-domain-specific communities are creating peer review processes to evaluate community-affiliated tools.
 
@@ -180,5 +182,3 @@ pyOpenSci was created to target these exact issues in support of open science.
 
 </div>
 </div>
-
-<!-- Bubbles sections... https://codepen.io/rinaw/pen/pGxorQ-->

_pages/python-packages.md

@@ -7,8 +7,8 @@ header:
     overlay_image: images/header.png
     overlay_filter: 0.6
 intro:
-    - excerpt: "The scientific Python packages below have
-    been accepted into the pyOpenSci ecosystem through our [open peer review process](/about-peer-review/)."
+    - excerpt: "The Python packages below have
+    been accepted into the pyOpenSci ecosystem through our [open software peer review process](/about-peer-review/)."
 toc: false
 classes: wide
 redirect_from:
@@ -20,21 +20,19 @@ redirect_from:
 {% assign packages_sorted = site.data.packages | sort_natural: 'date_accepted' | reverse %}
 {% assign total_packages = packages_sorted | size %}
 
+## Explore our accepted open source Python packages
 
-## Explore our accepted scientific Python open source packages
+To date, {{ total_packages }} packages have been accepted by pyOpenSci through our [open peer review process](https://www.pyopensci.org/about-peer-review/index.html). You can [check out the packages that are currently under review in our GitHub submission repository.](https://github.com/pyOpenSci/software-submission/issues)
 
-To date, {{ total_packages }} packages have been accepted into the pyOpenSci
-ecosystem. [Click here to check out packages that are currently under review.](https://github.com/pyOpenSci/software-submission/issues)
+[Click here to learn more about the process for submitting a package to pyOpenSci.](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html){: .btn  .btn--success }
 
 ### Community Partners
 
 To view packages affiliated with our partner communities that are a part of ourpeer review partnership program, click on a community link below. [Learn more about our community partnerships here.](/partners.html)
 
 <a href="/communities/astropy.html"><button class="button community">Astropy</button></a>
 
-### All Packages - Search and filters
-
-Below you can search and filter all of our packages.
+### Accepted pyOpenSci packages
 
 <p><input type="text" id="quicksearch" placeholder="Search" /></p>
 

_sass/minimal-mistakes/_archive.scss

@@ -88,6 +88,11 @@
   }
 }
 
+// make the titles in archive blocks full width
+h2.archive__item-title {
+  max-width: 100%;
+}
+
 .archive__item-teaser {
   position: relative;
   border-radius: $border-radius;
@@ -246,6 +251,10 @@
   margin-bottom: .02em; //used to be 2em
   // border-bottom: 1px solid $border-color;
 
+  h2 {
+    max-width: 100%;
+  }
+
   .archive__item-title {
     margin-bottom: 0;
   }

_sass/minimal-mistakes/_base.scss

@@ -15,7 +15,7 @@
     font-family: $global-font-family;
     line-height: 1.6;
     font-weight: $weight-3;
-    font-size: 1em;
+    font-size: 1rem;
 
     &.overflow--hidden {
       /* when primary navigation is visible, the content in the background won't scroll */
@@ -40,9 +40,9 @@
   // Use poppins for subheaders
   h2, h3, h4, h5, h6 {
     font-family: $header-font-family;
-    font-weight: $semibold-weight;
+    font-weight: $bold-weight;
     letter-spacing: -.03em;
-    line-height: .95em;
+    max-width: $medium;
   }
 
   h1 {
@@ -420,19 +420,6 @@
      Navigation lists
      ========================================================================== */
 
-  /**
-   * Removes margins, padding, and bullet points from navigation lists
-   *
-   * Example usage:
-   * <nav>
-   *    <ul>
-   *      <li><a href="#link-1">Link 1</a></li>
-   *      <li><a href="#link-2">Link 2</a></li>
-   *      <li><a href="#link-3">Link 3</a></li>
-   *    </ul>
-   *  </nav>
-   */
-
   nav {
     ul {
       margin: 0;

_sass/minimal-mistakes/_page.scss

@@ -82,12 +82,19 @@
     }
   }
 
+  // in our flowing layout the title should be max width
+  .page__content .pyos-section h2 {
+    max-width: 100%;
+
+  }
   .page__lead {
     font-family: $global-font-family;
     font-size: $type-size-5;
     font-weight: $weight-3;
   }
 
+
+
   .page__content {
     figure {
       max-width: 35rem;
@@ -101,9 +108,8 @@
     }
 
     h2 {
-      padding-bottom: 0.2em;
-      margin-bottom: 0.2em;
-      margin-top: 2.5em;
+      margin-bottom: 2.0rem;
+      margin-top: 4.1rem;
     }
 
     h1,
@@ -133,7 +139,7 @@
     p,
     dl {
       font-size: $type-size-5;
-      line-height: 1.5em;
+      line-height: 1.6rem;
     }
 
     /* paragraph indents */

_sass/minimal-mistakes/_pyos-cards.scss

@@ -41,21 +41,21 @@
         background-color: #fff;
         border: 1px solid #ddd;
         border-radius: 8px;
-        box-shadow: 0 4px 8px rgba(0, 0, 0, 0.1);
+        box-shadow: 0 6px 12px rgba(0, 0, 0, 0.1);
 
         .excerpt {
             font-size: 1em;
             padding: 1em;
         }
         h4.title {
-            color: $pyos-darkpurple!important;
-            font-size: 1.3em;
+            color: $pyos-deeppurple!important;
+            font-size: 1.4rem;
             margin: 0;
             font-family: $sans-serif;
-            font-weight: 500;
+            font-weight: 600;
         }
         .title-block {
-            background-color: $pyos-lightpurple;
+            background-color: #ecbee3;
             display: flex;
             height: 7em;
             padding: 1.2em;

_sass/minimal-mistakes/_pyos-grid.scss

@@ -174,10 +174,14 @@ $colors: (
   }
 
   p {
-    font-size: .9em;
+    font-size: 1em;
+    line-height: 1.8;
   }
 
   h2 {
+    font-size: 1.5rem;
+    margin-bottom: 1rem!important;
+
     a {
       text-decoration: none;
       font-size: 1.2em;
@@ -190,13 +194,13 @@ $colors: (
 
   h3.card__title.no_toc,
   .card__title.no_toc {
-    margin-top: .3em;
-    font-size: 1.5em;
-    color: #320a44;
+    margin-top: 1.2em;
+    font-size: 1.9em;
+    color: $pyos-darkpurple;
   }
 
   .page__meta.contributors {
-    font-size: .7em;
+    font-size: .9em;
   }
 
   .contributors a {
@@ -212,6 +216,7 @@ $colors: (
 
   ul a {
     text-decoration: none;
+    font-size: 1.2em
   }
 }