Owlet Weekly Update (Week of February 7)

Hello and welcome to another Owlet Weekly Update, friends! We have a bit of a lighter release this week, but we continue to build on our mission of ensuring that buttons and links take you to all of the correct places. Details below! 🔗

👍

We've been rolling out a redesigned docs experience for some time now—check out this page for the details!

The legacy docs style is now deprecated and is not receiving any bug fixes. All changes below are only applicable to the new docs experience (unless otherwise noted). We'll communicate a sunset timeline to any remaining legacy customers soon.

✨ New & Improved

• As previously mentioned, we’ve been hard at work re-thinking how Enterprise admins distinguish between user roles and how to simplify the process of managing multiple projects at scale. We’ve made some major improvements and our beta is now underway! This release includes even more improvements to this beta. If you're an Enterprise project administrator and you're curious about what we've been working on, we’d love for you to try it out! Drop us a line at [email protected]. 👥

🛠 Fixes & Updates

• There were certain situations where the “Clear Response” button in the API Reference wouldn’t do its one job of clearing responses. Thankfully, this release fixes that! 🚮
• Fixed an issue in the API Reference where arrays weren’t properly displaying their children if the children were certain polymorphic objects. 🚸
• A few minor Windows-friendly copy edits in certain places. 🪟
• A few small routing fixes for Enterprise projects. 🧭

Hope you're staying safe and healthy! Thanks for being a part of the ReadMe community, folks.

—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 week to the ReadMe Changelog) on the product updates we're shipping here at ReadMe. We'd love to hear what you think of these updates at [email protected]!