I've been hanging out and helping out in the Rust community for almost a couple years now (got up and running around August 2016). In that time, I've written a Twitter library that has helped people get their feet wet with the language, mentored newcomers to the language by answering questions in the "rust-beginners" IRC chatroom, and started contributing to the official documentation tool, rustdoc!
Over time I've shifted from being an educator in the community to being a contributor. Now, I'm the lead member of the Rustdoc Team, helping organize issue triage and reviewing new contributions to the documentation tool. Rustdoc has a lot of users and a lot of bug reports and feature requests, but not a lot of people who contribute to it primarily. That said, I've been able to implement a few cool things over the last few months:
- External doc files. This involved having to extend how rustdoc processes documentation from source code, and eventually required having to dip into the compiler to make sure the external files were being loaded correctly!
- Type links. (Well, part of them, anyway. This became a combined effort over time, but I got the initial code started for rustdoc's piece.) This was a doozy, requiring making rustdoc reach into the compiler for something it wasn't meant to handle at the time, extending our Markdown parser to make sure we could handle all the links correctly, and making sure all the links eventually came together in the final document. There's still so far to go on this, but it's taken quite the effort to get this far!
- The rustdoc readme (which was immediately ported to the Rust Compiler Internals Guide, hence the link). This is a technical overview of the rustdoc codebase, the processes it does to create docs, and how it fits into the compiler repository.