Astro continues to evolve how it works with and for its community.
Our community awards allow us to give back to those who volunteer their time submitting code and bug fixes, being welcoming and helpful in support threads, translating the docs, and enriching everyone’s Astro experience.
Previously a quarterly event, Astro recently committed to issuing these awards on a monthly basis. We also changed from peer-nominated awards to recipients chosen by our core maintainers.
This might sound less democratic, but we think of it like maintainer gratitude journaling: we ensure that our core maintainers are actively reflecting and on the lookout for the next crop of up-and-comers. We are proud to say that we dedicate time to our open-source community’s health, growth, and sustainability.
A community award is nice, but until now, this recognition has mostly stayed within our community. We wanted a better, more public, and more permanent place for community recognition. Somewhere you could show off to friends and family, maybe to explain where all those nights and weekends went!
We are thrilled to announce the launch of our first public community space: https://community.astro.build built by our first Community Engineer, Elian van Cutsem.
Today, you can visit and celebrate the people who helped make Astro the project you love to use. Stay tuned for more exciting community initiatives that will find a home there as we grow and extend the site!
Each week in our community calls we highlight and celebrate all the things our community builds with Astro. Today, we want to recognize a very special kind of community contribution that you might not normally see: the personal experiments and side projects that our own maintainers build for working on and contributing to Astro
Maintaining an open-source project means spending a lot of time in our code editors, in PRs, and on GitHub, looking things up in docs, keeping track of work-in-progress, and collaborating with others.
We’d like to showcase some of these tools we’ve built for our own use as we build Astro for (and with!) you. Some of these make routine tasks easier, and some just make them more fun… because that’s part of the point, too!
Maintainer Projects Showcase
Astro Docs Docs (AD²)contribute.docs.astro.build
Created by Sarah
Doc’ing Astro Docs! An entire site full of guides and resources for contributing to Astro Docs.
I have a Starlight problem! This project started as an easier way to organize and write than updating our existing guides as plain Markdown files in the GitHub repo. Every time I need to organize information, I create a new Starlight project. Shout out to Yan Thomas for providing all of our i18n content. Special thanks to Chris Swithinbank for his encouragement and support, and for insisting that this should actually be a deployed site for the Astro project!
Raycast ExtensionRaycast Store
Created by Elian
Reach and search the Astro Documentation in an instant right from Raycast without any hassle. Supports all languages that Astro Documentation supports & has all sidebar links that Astro Documentation has.
As a docs editor, I found myself constantly having to manually navigate to Astro Documentation and search for the right pages. I use Raycast all the time, so it seemed like a good solution to create an extension that sped up my docs writing & reviewing process.
Created by Marijn Kneppers
Let the bot do it for you! From creating a PTAL request to browsing the docs, Houston Bot is there to make the life of everyone working on/with Astro easier
As a support squad member, I got annoyed with having to switch over to a browser to search the docs, so I wrote a bot with a /docs command which allowed me to browse the docs from within Discord. This led to a /ptal (Please Take A Look) command to give maintainers an easier overview of the status of a pull request.
Starlight i18nVSCode Marketplace
Created by HiDeoo
Visual Studio Code extension to easily translate Starlight documentation pages using the built-in support for multilingual sites and git.
Being able to choose a supported language to translate from a Starlight configuration in a workspace repo and having side-by-side editors with the missing changes and the translated page seemed like a good idea, and I have been using it for all the translations I have submitted to the Starlight documentation so far.
Created by Hippotastic
Expressive Code is an engine for presenting source code on the web, aiming to make your code easy to understand and visually stunning. On top of accurate syntax highlighting powered by the same engine as VS Code, Expressive Code allows you to annotate code blocks using text markers, diff highlighting, code editor & terminal window frames, and more.
After I initially built these features into Astro Docs, users kept asking us how they could use our code snippets in their own projects. This led me to create Expressive Code as a standalone project, which actually became my first published set of NPM packages! I’m really happy that it’s already being used by Astro Docs, Starlight, and many individual websites.
Created by Yan Thomas
Lunaria is a localization management toolchain for open-source projects, allowing maintainers and contributors to keep track of their localization projects' progress sustainably and for free.
Lunaria came out of a desire to share the Astro Docs custom i18n translation status tracker, originally built by @hippotastic, with the wider open-source community. Lunaria was built for general compatibility and is suitable for a wide range of different content strategies, frameworks, and even git hosting platforms.
Created by Kevin & Otterlord
Create co-author messages to credit contributors 💜. This tool collects PR participants and creates a formatted co-author string for git commits.
At Astro, we highly value acknowledging our contributors. Our previous method involved quite a bit of manual work to search for an individual's git signature on GitHub so we could add them to a PR commit. Occasionally, this process took longer than the actual PR, but it was a worthwhile effort to show appreciation to our community.
Created by Alexander Niebuhr
Brand-new integration which adds an external remote image service to `astro:assets`. Your images will get a remote URL that optimizes them, similar to paid digital asset management services... but for free, if you have an Astro project! It works with every Astro adapter and hosting provider.
External Remote Image Optimization is either complex to set up or costs too much. Making this available to all Astro users for free makes Astro's Image story a lot better. The most complex thing to get right is authorization: how to make sure only Astro users can use it for free and having a fair-use policy in place.
Created by Erika
A dashboard showing stats about all the issues on every Astro repo. The idea is that by being able to visualize the total issue count as a graphical thing, it’ll “gamify” the act of bringing down the issue count.
After seeing the issue dashboard, Docs and Starlight felt the pressure to triage their issues and accepted the challenge. This brought down Astro's total issue count by 50 only a week after I released the website. (*Editor's note: Well played, Erika.)
Created by Nate & Chris
A centralized repository for reusable GitHub Action workflows. These actions help us automate common workflows across many different repositories in the withastro GitHub organization. The major benefit of having common workflows in a single location is that maintenance happens in one spot and is automatically rolled out to all of our repositories. Centralized workflows also make it much easier to set up automated workflows for brand new repositories.
When we first started building Astro, we had one central Astro monorepo for all of our code and documentation. This made it easy to share tooling and configuration but it became increasingly difficult to collaborate on many different focus areas as the project grew. While copying and pasting workflow files works for a small handful of repositories, the number of repositories began to grow in the summer of 2023. This automation repository is used by all of our repositories to share merge notifications in our Discord (congratsbot), format our source code with Prettier (format), and automate issue labeling (issue-opened and issue-labeled)
Created by Nate Moore
An Astro-branded Visual Studio Code theme featuring cool blues, minty greens, and soft purples and Astro’s mascot Houston.
Astro’s brand colors were begging to be turned into a syntax highlighting theme. With some adjustments for contrast and legibility, I am quite happy that this little experiment turned out so well. This theme has been downloaded by 12.5K people on the Visual Studio Code marketplace* and is the default theme for Astro’s Starlight documentation framework. (*Editors note: and 169 on the OpenVSX registry! 😉)
Live Astro Compilerlive-astro-compiler.vercel.app
Created by happydev
A playground for the Astro compiler that generates insightful previews of the compiled output of Astro components.
Sparked by the struggle of quickly spotting compiler bugs, I built this to save time on issue troubleshooting. Instead of diving straight into writing tests, now we can just toss some code into the playground, check out the output, and easily spot and show others what’s going wrong — making the whole debugging dance way smoother!
Created by Chris
Astro Badges celebrates Astro contributors with embeddable images featuring achievements unlocked by GitHub activity in the withastro organization. From Little Green Bug to Constellation Crafter, every one of Astro’s almost 3,500 contributors is here!
Astro Badges started as a weekend project after I noticed the badg.es domain was available. It’s grown a lot since then, including a full redesign in collaboration with Astro’s designer, @doodlemarks. Probably the most challenging thing about maintaining it is coming up with fun achievement names, although @sarah11918 is always game to workshop them! My favorite recent addition is probably the SSRsly achievement for people working on Astro’s serverless adapters. Shout out to @Yan-Thomas, @ElianCodes, @natemoo-re, @mayank99, @torn4dom4n, @jacobthesheep, and @TheOtterlord for contributing along the way 🙌