Hello and happy ~~Tuesday~~ Thursday—hope you had a safe and enjoyable Thanksgiving holiday! To offset the absolutely devastating amount of pumpkin pie I consumed last week, we’ve reduced the size of our site bundles, along with a bunch of other good stuff(ing?). Details below! 🥧

✨ New & Improved

From the people that brought you dash.readme.io comes its equally entertaining sequel—dash.readme.com! You’ve been able to access the project dashboard via dash.readme.com for a while, but you may have noticed your web browser redirecting to the new URL in the last couple weeks. And rest assured, your requests to the ReadMe API should work as normal for the foreseeable future! 🔗
Much like preparing a turkey for Thanksgiving dinner, preparing an OpenAPI file can be a grueling process that often requires a helping hand. Fortunately, we’ve made a small update to our API onboarding process that makes it even easier to get in touch with our incredible support team! (EDITOR’S NOTE: Please do not contact our support team with your turkey-related inquiries. But if you have a story about your turkey-making experiences this year,tweet at us!) 🤝
Hey, have you heard about our latest and greatest enterprise feature—Staging? You should definitely hit us up to try it out! We’ve been getting a lot of great feedback on it and have been making a lot of great improvements behind the scenes. This release includes some of those! 🌱
As alluded to above, we’ve slashed away at the size of our main bundle that’s loaded in on all documentation sites (with more updates to come in the future!). What does that mean? Faster, lighter pages for your users! ⚡
A few readability improvements to our Node.js code samples in the API Explorer. 🤓

🛠 Fixes & Updates

Don’t you hate when Google Maps navigates you to your local post office, only for you to pull up to a fenced off building that’s been fully burned to the ground for months? Well fun (and 100% true) fact: that happened to me a few weeks ago here in Minneapolis! In the spirit of Google Maps (which continues to insist that that post office exists and is open despite the feedback I've submitted), I can happily report that this release includes a fix to an issue where certain URLs in ReadMe would 301 instead of 404. Sorry for the misdirection, folks! 🗺️
A couple of tiny updates to the API logs to make them a little friendlier to response bodies that don’t exactly conform to the JSON way of life (in other words… response bodies that aren’t JSON). 🧬
Not everyone on our team can be on Shinae’s level, unfortunately. As with releases of yore, this one includes fixes to a few glaring spelling and grammar issues in some of our product copy. ✏️
Improvements to some of the number-crunching that takes place in the API Metrics Dashboard. 📈

If you haven't already, please take some time to learn about Indigenous rights and the National Day of Mourning. And if you can, please support theIndigenous-led fight to Stop Line 3. Thanks for tuning in and for being a part of the ReadMe community!

—Kanad and the ReadMe Team

📘
What is the Owlet Weekly Update?
Thanks for tuning in to another edition of our Owlet Weekly Update—an owlet-sized update (posted every Tuesday to the ReadMe Changelog) where we provide an overview of the product updates that went out as part of our new Tuesday release cycle. As we refine our format and process for providing these updates, we'd love to hear what you think at support@readme.io!