diff --git a/images/astropy_project_logo.svg b/images/astropy_project_logo.svg
new file mode 100644
index 00000000..890ea7f5
--- /dev/null
+++ b/images/astropy_project_logo.svg
@@ -0,0 +1,123 @@
+
+
+
diff --git a/partners/astropy.md b/partners/astropy.md
new file mode 100644
index 00000000..d740813c
--- /dev/null
+++ b/partners/astropy.md
@@ -0,0 +1,42 @@
+# pyOpenSci's partnership with Astropy
+
+:::{figure-md} astropy-logo
+:class: myclass
+
+
+
+...
+:::
+
+pyOpenSci has a collaboration with the [Astropy scientific community](https://www.astropy.org/). Through this collaboration we add an additional layer of peer review checks to Astropy-related packages that go through our [open peer review process](https://www.pyopensci.org/software-peer-review/about/intro.html). If the package meets both the Astropy criteria and our pyOpenSci peer review criteria, it can then become both an astropy affiliated package and a pyOpenSci ecosystem package.
+
+If you are submitting a package for review and wish to also apply for astropy affiliation, your package will be:
+Reviewed against current pyOpenSci guidelines and checks.
+Also reviewed against the Astropy-specific guidelines listed below.
+
+If you are submitting a package for review and wish to also apply for astropy affiliation, your package will be:
+
+- Reviewed against current pyOpenSci guidelines and checks.
+- Also reviewed against the Astropy-specific guidelines listed below.
+
+(astropy-collaboration)=
+
+### Astropy Specific Software Peer Review Guidelines
+
+To be an affiliated astropy package, your package should:
+
+- Be useful to astronomers. This can mean useful to a specific sub-domain of astronomy, or more broadly useful to a large fraction of astronomy (or beyond, as long as it is also useful for astronomy).
+- Specifically use, interface with, or provide complementary capabilities to other Astropy packages.
+- Use classes and functions from the astropy core package wherever possible and appropriate, and (as much as possible) avoid duplication with other packages in the Astropy ecosystem. This facilitates re-use of code and sharing of resources.
+
+### Ecointegration - Integration with the Astropy Ecosystem
+
+Your package should clearly integrate into the broader Astropy ecosystem. It should:
+
+- Use Astropy or other affiliated packages wherever possible
+- Use / depend upon Astropy or other affiliated packages functionality wherever possible to avoid duplication of functionality across the ecosystem.
+
+## Long-term maintenance & affiliate status over time
+
+Note however that if packages become unmaintained or do not meet the standards anymore, they may be removed from the list of affiliated packages.
+This rule applies to any package that applies for affiliated status with a specific domain community through the pyOpenSci partnership program.
diff --git a/partners/scientific-communities.md b/partners/scientific-communities.md
index cafd66ec..4ecc7a54 100644
--- a/partners/scientific-communities.md
+++ b/partners/scientific-communities.md
@@ -6,6 +6,7 @@
About Our Partnerships
JOSS
+Astropy
Pangeo
```
+
+...
+:::
+
+pyOpenSci has a collaboration with the [Astropy scientific community](https://www.astropy.org/). Through this collaboration we add an additional layer of peer review checks to Astropy-related packages that go through our [open peer review process](https://www.pyopensci.org/software-peer-review/about/intro.html). If the package meets both the Astropy criteria and our pyOpenSci peer review criteria, it can then become both an astropy affiliated package and a pyOpenSci ecosystem package.
+
+If you are submitting a package for review and wish to also apply for astropy affiliation, your package will be:
+Reviewed against current pyOpenSci guidelines and checks.
+Also reviewed against the Astropy-specific guidelines listed below.
+
+If you are submitting a package for review and wish to also apply for astropy affiliation, your package will be:
+
+- Reviewed against current pyOpenSci guidelines and checks.
+- Also reviewed against the Astropy-specific guidelines listed below.
+
+(astropy-collaboration)=
+
+### Astropy Specific Software Peer Review Guidelines
+
+To be an affiliated astropy package, your package should:
+
+- Be useful to astronomers. This can mean useful to a specific sub-domain of astronomy, or more broadly useful to a large fraction of astronomy (or beyond, as long as it is also useful for astronomy).
+- Specifically use, interface with, or provide complementary capabilities to other Astropy packages.
+- Use classes and functions from the astropy core package wherever possible and appropriate, and (as much as possible) avoid duplication with other packages in the Astropy ecosystem. This facilitates re-use of code and sharing of resources.
+
+### Ecointegration - Integration with the Astropy Ecosystem
+
+Your package should clearly integrate into the broader Astropy ecosystem. It should:
+
+- Use Astropy or other affiliated packages wherever possible
+- Use / depend upon Astropy or other affiliated packages functionality wherever possible to avoid duplication of functionality across the ecosystem.
+
+## Long-term maintenance & affiliate status over time
+
+Note however that if packages become unmaintained or do not meet the standards anymore, they may be removed from the list of affiliated packages.
+This rule applies to any package that applies for affiliated status with a specific domain community through the pyOpenSci partnership program.
diff --git a/partners/scientific-communities.md b/partners/scientific-communities.md
index cafd66ec..4ecc7a54 100644
--- a/partners/scientific-communities.md
+++ b/partners/scientific-communities.md
@@ -6,6 +6,7 @@
About Our Partnerships