I want to highlight something that I appreciate in your release post, which is the short explanation between paragraphs 1 & 2:
"Sway is an i3-compatible Wayland desktop for Linux and FreeBSD"
One of my major peeves with OSS projects is the tendency to adopt an "if you're reading this, you already know what this is for" stance. It's not just elitist... it's a missed opportunity to bring passers-by into the fold.
It might seem dull or repetitive to people that are deep in the trees to see layman explanations, but at least linking to them is a small but appreciated nod of respect to people who are just coming online.
To this end, I would challenge that you could set an amazing example that goes further towards accomplishing these goals by linking the words in that description to readable explanations of what the words mean in the context of this project. Your goal should be to move beyond what Sway is and perhaps start with why Sway exists. It's clear that this is important, but someone coming in has no idea what motivated you and your army of contributors to stop other important projects and build this. Where does it fit into the concepts that they are already familiar with? What other technologies does it replace? What can I do with this that I couldn't do before? Are there tradeoffs to using this over other solutions? Are there situations where I shouldn't use this? And eventually: are there newer projects that Sway inspires which are even better that I should probably be using instead?
If we look at your explanation in this new light, "Sway is an i3-compatible Wayland desktop for Linux and FreeBSD", you can see that it's opaque to people who aren't already familiar. i3... you mean like the Intel i3? What's Wayland? I use Ubuntu... isn't that my desktop? I heard MacOS is based on FreeBSD, so can I use this on a Mac?
These aren't problems, they are opportunities to be a hero to the silent majority of people who have no freaking clue what a tiling window manager is or why it might be applicable to them.