Owlet Weekly Update (Week of February 15)

Hello and welcome to another weekly update! I know I keep teasing it, but we're hard at work on several new ReadMe experiences and improvements that we'll be sharing news on very soon. But the wins are not just long-term, folks! This week includes a lot of behind-the-scenes improvements so our engineers can build and ship much faster (hello, npm 7!) and we also shipped a few small wins on the API Explorer and Firefox front. Details below! 🦊

✨ New & Improved

• This release includes lots of little improvements to the API Explorer—more secure Ruby code snippets, better rendering of response array parameter descriptions, and improved support for content declarations! Oh, and we got rid of array keys in the response renderer in a desperate (but successful!) effort to declutter our lives. 🧹
• White text on a white background is very difficult to read, y'all—would strongly advise against it. Apologies if you previously had to do so when applying for an open source plan in the dashboard. 🏳️

🛠 Fixes & Updates

• There was an issue where document fragment links weren't properly navigating to the correct section for select users on Firefox. Well we're cranking the Van Halen up to 11 in this week's release in hopes that Firefox browsers will "jump!" to the correct section. 🤘
• Several tiny URL fixes in the project dashboard for enterprise projects that are using Staging. 🔗

Thanks for reading and 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]!