fix: cleanup styles for readability

Author: lwasser

_pages/how-to-submit.md

@@ -14,17 +14,17 @@ toc: true
 
 
 
-## <i class="fa-solid fa-rocket" style="color:#a193c6"></i> Submit Your Python Package for pyOpenSci Review
+## <i class="fa-solid fa-rocket" style="color:#a193c6"></i> Submit your Python package for review
 
 You’ve created a Python package—now what? How do you ensure it follows best practices, is well-documented, and reaches the right audience?
 
 **pyOpenSci’s peer review process** connects you with experts who will help refine your package’s structure, documentation, and usability. Accepted packages become part of our vetted ecosystem, increasing their visibility and credibility. You may also have the opportunity to publish in the [Journal of Open Source Software (JOSS)](https://www.pyopensci.org/software-peer-review/partners/joss.html).
 
 
-### <i class="fa-solid fa-circle-chevron-down" style="color:#a193c6"></i> Why submit a Python package for software peer review?
-- <i class="fa-solid fa-eye" style="color:#81c0aa;"></i> **Visibility & support:** Gain expert feedback on your code, documentation, and packaging.
-- <i class="fa-solid fa-check-circle" style="color:#81c0aa;"></i> **Quality & best practices:** Ensure your package follows open-source and scientific standards.
-- <i class="fa-solid fa-book-open" style="color:#81c0aa;"></i> **JOSS publication:** Get the option to publish in the Journal of Open Source Software (JOSS) after acceptance.
+### <i class="fa-solid fa-circle-chevron-down"></i> Why submit a Python package for software peer review?
+- <i class="fa-solid fa-eye" style="color:#8B868E"></i> **Visibility & support:** Gain expert feedback on your code, documentation, and packaging.
+- <i class="fa-solid fa-check-circle" style="color:#8B868E"></i> **Quality & best practices:** Ensure your package follows open-source and scientific standards.
+- <i class="fa-solid fa-book-open" style="color:#8B868E"></i> **JOSS publication:** Get the option to publish in the Journal of Open Source Software (JOSS) after acceptance.
 
 <i class="fa-solid fa-book" style="color:#81c0aa;"></i> **[Learn more about the benefits of our peer review process](https://www.pyopensci.org/software-peer-review/about/benefits.html)**
 
@@ -117,8 +117,20 @@ Once your have determined that you package it in scope and meets our core packag
       More....
     </figcaption>
 </figure>
+
 Once submitted, our editors will review your issue and guide you through the next steps.
 
+### <i class="fa-solid fa-check" style="color:#81c0aa;"></i> Guidelines for filling out the issue template
+
+* **Complete all sections of the template.** If you have questions about fields, you can ask about them in the review issue.
+* **Do not modify existing formatting:** Please do not modify the template structure by adding elements to the template fields such as bold, italics, etc.
+* **Submit your issue only when fully completed:** If you can, try to avoid submitting an issue and then continuously editing it. If you'd like to work on the issue over time, consider forking our repository and working on the issue in your fork before submitting it as an option.
+* **If you made a pre-submission enquiry**, paste the link to the corresponding issue in your issue submission to link your submission request to the pre-submission discussion.
+
+<div class="notice notice--info" markdown="1">
+<i class="fa-solid fa-circle-exclamation" style="color:#81c0aa;"></i> **Why does filling out our review template matter?**
+Our peer review workflow relies on scripts to process submission data. If the template structure is modified, it will break our automated processes!
+</div>
 
 ### <i class="fa-solid fa-list-check" style="color:#81c0aa;"></i> Choose the correct submission type
 
@@ -149,26 +161,13 @@ If you need help getting your package ready for review, you can submit a help re
 
 </div>
 
-### <i class="fa-brands fa-github-alt" style="color:#81c0aa;"></i> Understanding our GitHub issue submission process
-
-When you submit your package for review, you will **fill out a GitHub issue template**. This structured template helps our editorial board evaluate your package efficiently. This section helps you understand the elements of the template.
-
-### <i class="fa-solid fa-check" style="color:#81c0aa;"></i> Guidelines for filling out the issue template
-
-* **Complete all sections of the template.** If you have questions about fields, you can ask about them in the review issue.
-* **Do not modify existing formatting:** Please do not modify the template structure by adding elements to the template fields such as bold, italics, etc.
-* **Submit your issue only when fully completed:** If you can, try to avoid submitting an issue and then continuously editing it. If you'd like to work on the issue over time, consider forking our repository and working on the issue in your fork before submitting it as an option.
-* **If you made a pre-submission enquiry**, paste the link to the corresponding issue in your issue submission to link your submission request to the pre-submission discussion.
-
-<div class="notice notice--info" markdown="1">
-<i class="fa-solid fa-circle-exclamation" style="color:#81c0aa;"></i> **Why does filling out our review template matter?**
-Our peer review workflow relies on scripts to process submission data. If the template structure is modified, it will break our automated processes!
-</div>
+## <i class="fa-brands fa-github-alt" style="color:#81c0aa;"></i> About our GitHub issue submission process
 
+The structured template of our GitHub issue helps our editorial board evaluate your package efficiently. This section will help you understand some of the core elements of our template.
 
 ### <i class="fa-solid fa-eye-slash" style="color:#81c0aa;"></i> Sections you can ignore
 
-Some sections of the template are **for editors only** and should be left blank. These include:
+Some template sections are **for editors only** and should be left blank. These include:
 
 - **Editorial assignments:** "EiC," "Editor," "Reviewer 1," "Reviewer 2"
 - **JOSS-specific fields:** "JOSS DOI," "Version accepted," "Date accepted"
@@ -185,11 +184,35 @@ Version accepted: TBD
 Date accepted (month/day/year): TBD
 ```
 
+### JOSS publication
+
+One of the benefits of submitting your package to pyOpenSci for review is that once it's approved, it can be fast-tracked for publication with [JOSS](https://joss.theoj.org/). JOSS accepts pyOpenSci's review as theirs, and therefore, you will not need to go through another full review. Instead, JOSS will only review your paper.md file.
+
 ### <i class="fa-solid fa-users" style="color:#81c0aa;"></i> Community partnerships
 
-We collaborate with domain-specific organizations to ensure high-quality reviews. If you are interested in becoming an affiliated project associated with one of our partners, you can click on the partner that your package's scope aligns with. Our most active partnership is with [Astropy](https://www.pyopensci.org/software-peer-review/partners/astropy.html).
 
-If your package fits within one of our partnerships, we will assign an editor who is able to review your package for both OpenSci requirements and the affiliation project affiliation.
+We collaborate with [domain-specific organizations](https://www.pyopensci.org/software-peer-review/partners/scientific-communities.html) that run their own package review processes. Instead of undergoing **separate reviews**, you package can be considered for affiliation with three organizations in **one streamlined pyOpenSci review**.
+
+If your package fits within a partnered domain, we will assign an editor familiar with both **pyOpenSci’s** and the affiliated community’s **review standards**.
+This allows your package to:
+
+- **Gain community affiliation** (for example, Astropy for astronomy-related packages).
+- **Join pyOpenSci’s vetted ecosystem** as a recognized open source tool.
+- **Optionally be fast-tracked for publication in JOSS** after pyOpenSci acceptance.
+
+**[Astropy](https://www.pyopensci.org/software-peer-review/partners/astropy.html)** is currently our most active partnership.
+
+*Below is the template if you want to be considered for partner-community affiliation.*
+
+```markdown
+
+## Community Partnerships
+
+If your package is associated with an existing community please check below:
+
+- [ ] Astropy:[My package adheres to Astropy community standards](https://www.pyopensci.org/software-peer-review/partners/astropy.html)
+- [ ] Pangeo: My package adheres to the [Pangeo standards listed in the pyOpenSci peer review guidebook][PangeoCollaboration]
+```
 
 <figure>
   <source srcset="/images/peer-review/pyos-partnerships-peer-review.webp" type="image/webp">
@@ -200,44 +223,50 @@ If your package fits within one of our partnerships, we will assign an editor wh
   </figcaption>
 </figure>
 
-### <i class="fa-solid fa-pen-to-square" style="color:#81c0aa;"></i> Double check your your submission before hitting submit
 
-Before submitting your issue, double-check that all fields are filled out correctly. You can use the GitHub preview tab to ensure the issue looks correct. Check the following things:
+### Code of conduct & package maintenance commitment
 
-✅ The issue is **fully completed**
-✅ The template **formatting has not been changed**
-✅ The **Write tab preview looks correct**
+To be considered for review, you must agree to both:
+1. **Follow our Code of Conduct:** Ensure respectful and constructive collaboration.
+2. **Commit to package maintenance:** Keep your package updated after acceptance.
 
-## TODO: add screenshot of the preview
 
-<div class="notice notice--tip" markdown="1">
-One of the quirky things about the pyOpenSci submission template is that checkboxes have two completion methods:
-- You can manually add an "X" inside the box (`[X]`).
-- Or, after submission, click the box to check it off.
-</div>
+```markdown
+## Code of Conduct & Commitment to Maintain Package
 
-Need more Markdown help? Check out this [Markdown Guide](https://www.markdownguide.org/basic-syntax/).
+- [ ] I agree to abide by [pyOpenSci's Code of Conduct][PyOpenSciCodeOfConduct] during the review process and in maintaining my package after should it be accepted.
+- [ ] I have read and will commit to package maintenance after the review as per the [pyOpenSci Policies Guidelines][Commitment].
+```
 
+#### <i class="fa-solid fa-comments" style="color:#81c0aa;"></i> Code of conduct: constructive collaboration
 
-Once you're ready, **submit your issue**, and our editors will take it from there! 🚀
+pyOpenSci’s peer review is a **collaborative process** focused on **improving your package**.
+We require all maintainers, reviewers, and editors to follow our [Code of Conduct](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html) to ensure discussions remain **professional, constructive, and respectful**.
 
-#### Code of Conduct & Commitment to Maintain Package
 
-In order for your package to progress through the pyOpenSci review process, you'll need to check both of the [Code of Conduct](https://www.pyopensci.org/handbook/CODE_OF_CONDUCT.html) agreement as well as the [maintenance agreement](https://www.pyopensci.org/software-peer-review/our-process/policies.html#after-acceptance-package-ownership-and-maintenance) outlined in the [pyOpenSci Policies Guidelines](https://www.pyopensci.org/software-peer-review/about/intro.html). You can indicate your agreement in one of two ways:
+#### <i class="fa-solid fa-wrench" style="color:#81c0aa;"></i> Package maintenance: sustaining a curated ecosystem
+
+Our peer review process aims to build a **trusted ecosystem of well-maintained scientific Python packages**. Maintainers should expect to **actively maintain** their package for at least **2 years** after acceptance.
+
+If your primary goal is publication rather than ongoing package maintenance, consider submitting directly to [JOSS](https://joss.theoj.org/) instead.
+
+<!--
+You can indicate your agreement in one of two ways:
 * adding an "X" (without quotation marks) inside the brackets in the Markdown version of the issue, so that it reads like this: [X]
 * submitting the issue without making any changes to this section, and then clicking on the checkboxes when they're rendered in the submitted issue.
+ -->
 
-<!-- #### For all submissions
+## TODO: add screenshot of the preview
 
-This section is important, as it helps us more holistically evaluate your package and determine whether or not it's a good fit for pyOpenSci review. Each of the following sections should be addressed/answered:
-* *Explain how and why the package falls under the categories you indicated above.* Here's where you'll provide us with information that connects your package and its functionality to both its domain and technical capabilities.
-* *Who is the target audience and what are scientific applications of this package?* This helps us understand who will be using the package.
-* *Are there other Python packages that accomplish the same thing? If so, how does yours differ?* This helps us get a handle on other packages that fall within the same domain, as well as ensure that efforts aren't being duplicated.
- -->
+<div class="notice notice--tip" markdown="1">
+One of the quirky things about the pyOpenSci submission template is that checkboxes have two completion methods:
+- You can manually add an "X" inside the box (`[X]`).
+- Or, after submission, click the box to check it off.
 
-#### Publication Options
+Need more Markdown help? Check out this [Markdown Guide](https://www.markdownguide.org/basic-syntax/).
+</div>
 
-One of the benefits of submitting your package to pyOpenSci for review is that once it's approved, it can be fast-tracked for publication with [JOSS](https://joss.theoj.org/). JOSS accepts pyOpenSci's review as theirs, and therefore you will not need to go through another full review. Instead, JOSS will only review your paper.md file.
+Once you're ready, **submit your issue**, and our editors will take it from there! 🚀
 
 #### Please fill out our survey
 
@@ -258,10 +287,12 @@ During this process, editors may request **minor updates** to help your package
 
 📖 **Read the full review process in our** [Peer Review Guide](https://www.pyopensci.org/software-peer-review/how-to/author-guide.html).
 
+<div class="notice notice--info" markdown="1">
 ## <i class="fa-regular fa-comments"></i> Connect with us!
 
-If you found this how-to guide useful, or if you have suggestions for how to improve it, we'd love to hear from you! Reach out to us on:
+If you found this how-to guide useful, or if you have suggestions for improving it, we'd love to hear from you! Reach out to us on:
 
 * [BlueSky]()
 * [Fosstodon](https://fosstodon.org/@pyOpenSci),
 * [LinkedIn](https://www.linkedin.com/company/pyopensci),
+</div>

_sass/minimal-mistakes/_base.scss

@@ -233,6 +233,159 @@
       }
   blockquote.highlight-quote.purple:after{
       color: $pyos-mediumpurple;
+    }
+  }
+
+
+  @include breakpoint('max-width: #$mobile') {
+    padding: 0;
+    //font-size: 2rem;
+  }
+}
+
+// for some reason i have to manually override here
+blockquote.highlight-quote.magenta:after{
+    color: $pyos-magenta;
+    }
+blockquote.highlight-quote.purple:after{
+    color: $pyos-mediumpurple;
+    }
+
+/* links */
+
+a {
+  text-underline-offset: .1em;
+  text-decoration-color: rgba($text-color, 0.7);
+  text-decoration: underline;
+
+
+  &:focus {
+    @extend %tab-focus;
+  }
+
+  &:visited {
+    color: $link-color-visited;
+  }
+
+  &:hover {
+    color: $link-color-hover;
+    outline: 0;
+    text-decoration: none !important;
+    text-decoration-line: none !important;
+    transition: color 0.3s ease, text-decoration-color 0.3s ease;
+  }
+}
+
+/* buttons */
+
+button:focus {
+  @extend %tab-focus;
+}
+
+/* code */
+
+tt,
+code,
+kbd,
+samp,
+pre {
+  font-family: $monospace;
+  font-weight: $weight-5;
+  font-size: 1em;
+}
+
+
+
+
+kbd {
+    background-color: $kbd-color-background;
+    color: $kbd-color-text;
+    border-radius: 0.25rem;
+    box-shadow: 0 2px 0 1px $kbd-color-border;
+    line-height: 1;
+    font-size: .75em;
+    padding: .15em .25em;
+
+    &:hover {
+         box-shadow: 0 1px 0 0.5px $kbd-color-border;
+         top: 1px;
+  }
+}
+
+pre {
+  overflow-x: auto; /* add scrollbars to wide code blocks*/
+}
+
+/* horizontal rule */
+
+hr {
+  display: block;
+  margin: 1em 0;
+  border: 0;
+  border-top: 1px solid $border-color;
+}
+
+/* lists */
+
+ul,
+ol {
+  margin-bottom: 1.9em;
+  font-weight: $weight-3;
+}
+ul li,
+ol li {
+  margin-bottom: 0.3em;
+  font-size: $type-size-5;
+  list-style: 1.4em;
+}
+
+ul li::marker {
+    color: #9C939F;  /* Change bullet color */
+}
+
+li ul,
+li ol {
+  margin-top: 0.5em;
+}
+
+/*
+   Media and embeds
+   ========================================================================== */
+
+/* Figures and images */
+
+figure {
+  display: -webkit-box;
+  display: flex;
+  -webkit-box-pack: justify;
+  justify-content: space-between;
+  -webkit-box-align: start;
+  align-items: flex-start;
+  flex-wrap: wrap;
+  margin: 2em 0;
+
+  img,
+  iframe,
+  .fluid-width-video-wrapper {
+    margin-bottom: 1em;
+  }
+
+  img {
+    width: 100%;
+    border-radius: $border-radius;
+    -webkit-transition: $global-transition;
+    transition: $global-transition;
+  }
+
+  > a {
+    display: block;
+  }
+
+  &.half {
+    > a,
+    > img {
+      @include breakpoint($small) {
+        width: calc(50% - 0.5em);
       }
 
   /* links */