diff --git a/content/blog/2025/openscapes-readme-contribution/index.md b/content/blog/2025/openscapes-readme-contribution/index.md
new file mode 100644
index 000000000..2b8f54684
--- /dev/null
+++ b/content/blog/2025/openscapes-readme-contribution/index.md
@@ -0,0 +1,28 @@
+---
+title: A helpful contribution to our JupyterHub SSH README from OpenScapes
+date: 2025-10-21
+categories: community-impact
+tags:
+  - open-source
+  - foundational-contribution
+---
+
+We love when collaborators contribute back to the tools we maintain! Andy Teucher from [OpenScapes](../../../collaborators/openscapes/) recently [fixed a documentation issue](https://github.com/yuvipanda/jupyter-sshd-proxy/pull/11) in `jupyter-sshd-proxy` that benefits everyone using the tool.
+
+[`jupyter-sshd-proxy`](https://github.com/yuvipanda/jupyter-sshd-proxy) is a tool originally created by Yuvi to help 2i2c communities connect to their JupyterHub instances via SSH. Andy ran into an issue when using it with the VS Code fork that uses the [`open-remote-ssh`](https://github.com/jeanp413/open-remote-ssh) extension - it failed unless double quotes were used around the authorization token in the `ProxyCommand`.
+
+Through experimentation, Andy figured out the fix and [contributed it back to the README](https://github.com/yuvipanda/jupyter-sshd-proxy/pull/11). Now everyone using this tool will have clearer documentation.
+
+While small, we think this is a nice example of a ["Foundational contributions"](../foundational-contributions/index.md) from a community:
+
+- 2i2c creates and maintains open source tools to help our communities
+- Our communities use those tools and run into issues
+- They debug, figure out solutions, and contribute improvements back
+- Everyone benefits from the improvements
+
+This is exactly how we want 2i2c to help our communities - by making it easy for them to contribute back to the ecosystem and strengthen the tools everyone relies on.
+
+## Acknowledgements
+
+- Thanks to [Andy Teucher](https://github.com/ateucher) for the contribution and debugging!
+- Thanks to [OpenScapes](../../../collaborators/openscapes/) for being great collaborators places where can work with people like Andy
diff --git a/content/blog/2025/web-traffic-tracking-open-source/featured.png b/content/blog/2025/web-traffic-tracking-open-source/featured.png
new file mode 100644
index 000000000..17928f8d3
Binary files /dev/null and b/content/blog/2025/web-traffic-tracking-open-source/featured.png differ
diff --git a/content/blog/2025/web-traffic-tracking-open-source/index.md b/content/blog/2025/web-traffic-tracking-open-source/index.md
new file mode 100644
index 000000000..a3e182f9c
--- /dev/null
+++ b/content/blog/2025/web-traffic-tracking-open-source/index.md
@@ -0,0 +1,45 @@
+---
+title: "TIL: A few ways to track web traffic for open source projects"
+date: "2025-10-19"
+authors:
+  - Chris Holdgraf
+categories:
+- learning
+tags:
+- community
+- open-source
+---
+
+Understanding how people discover and navigate your project's web presence is valuable for open source communities, but there are a lot of options out there and many maintainers may not know about them. Recently Chris did some research to improve the web analytics for [Jupyter](https://jupyter.org), and learned about several options for tracking web traffic[^1]. Here's a quick report of what stood out. 
+
+[^1]: Chris has been [serving on the Jupyter Executive Council](../executive-council-updates/) as a [Foundational contribution](../foundational-contributions/). This was related to that effort!
+
+## Three analytics tools we found helpful
+
+**[Plausible.io](https://plausible.io/)** - A privacy-friendly, GDPR-compliant analytics service
+- Clean interface with public dashboards (see [Jupyter's dashboard](https://plausible.io/jupyter.org))
+- Paid service but offers 15% discount for open source projects
+- Cost scales with traffic volume. It can get expensive for a project as big as Jupyter!
+- This is the service we ultimately ended up using...
+
+**[ReadTheDocs Analytics](https://docs.readthedocs.com/platform/stable/traffic-analytics.html)** - Built-in traffic tracking for documentation sites
+- Available as a free add-on for ReadTheDocs projects, it provides traffic data specific to documentation pages.
+- There's no additional cost if already using ReadTheDocs, though if you're on a business plan you may need to pay for it.
+- The analytics are a bit barebones, but quite useful for learning where your readers are navigating.
+- Enable in `Settings` > `Addons` > `Analytics`.
+
+**[GitHub Repository Analytics](https://docs.github.com/en/repositories/viewing-activity-and-data-for-your-repository/viewing-traffic-to-a-repository)** - Native analytics in GitHub.
+- Shows clones, views, and referring sites. This is also fairly barebones, but it's really useful to see who is actually looking at your repository.
+- Free for all GitHub repositories.
+- Access via `Insights` > `Traffic` on any repository.
+
+## Learn more
+
+- [GitHub issue coordinating Jupyter's analytics work](https://github.com/jupyter/jupyter.github.io/issues/815)
+- [Plausible.io public dashboard for jupyter.org](https://plausible.io/jupyter.org) (this might be down for now, but we're working to bring it back up)
+- [ReadTheDocs Analytics documentation](https://docs.readthedocs.com/platform/stable/traffic-analytics.html)
+- [GitHub Traffic Analytics API](https://docs.github.com/en/rest/metrics/traffic?apiVersion=2022-11-28)
+
+## Acknowledgements
+
+Thanks in particular to [Jason Grout](https://github.com/jasongrout) from the [Jupyter Executive Council](/collaborators/jupyter/) for collaborating on this investigation and helping test these tools.