Hello and welcome to another weekly update, friends! With the northern hemisphere's ongoing deprecation of leaves, it's fitting that we ship support for the deprecated keyword in the API Reference! We're also working on some big upcoming metrics updates, shipping more Slack App updates, and fixing a few bugs. More below! 🍂

👍

We've been rolling out a redesigned docs experience for some time now—check out this page for the details! Changes that are only applicable to the redesigned docs experience will be prefixed with a 🆕 emoji. The legacy docs style will be deprecated on December 31, 2021.

✨ New & Improved

• 🆕 With the deprecation of Mercury Retrograde, Daniel Craig as James Bond, Ryan from the Bachelorette... the deprecation jokes write themselves and I could go on forever, but the main takeaway is that our API Reference now supports the deprecated keyword! Now, if you upload an OpenAPI file with deprecated endpoints and/or deprecated parameters, the API reference section will surface several hints to your users that it's time to get with the times. Check out an example here! 🌹
• As we continually allude to, we're working on some exciting updates to the metrics experience! This release includes even more of behind-the-scenes work so it's ready for primetime. We have a sneak peek event on November 2nd—you canRSVP here! 📆
• As part of upcoming changes mentioned above, the weekly Slack updates on your documentation and API metrics have now been refreshed to send you even better insights than before! Oh, and it should actually hit your Slack inbox as expected. 📰
• 🆕 For those of you with lively developer communities that are constantly blowing up your discussion forums, we've added pagination to the bottom of the main discussion forum page so it's easier to navigate through all the banter. 🗣

🛠 Fixes & Updates

• 🆕 Seeing as I have zero professional titles, I was always thrown off by this bit where white people at my high school would jokingly call me "Dr. Gupta". Cut it out Noah, I am literally 16 years old and I am not related to CNN's chief medical correspondent! Have you seen his hairline? Anyways, we had an issue where certain fields in the API Reference were being denoted by their title values, rather than their names. While this release won't fix Western culture's hazy understanding of South Asian surnames, this release eliminates some of the confusion with fields in the reference section. 📛
• 🆕 There was an issue where schema types were inadvertently displaying with a capitalized first letter. This release restores these schema types to their true form. 🌱
• Seeing as society as a whole does not care about the casing in your email address, we are now adhering to this social norm when you've forgotten your password. 📧
• 🆕 Fixed an issue where certain characters weren't properly rendering in the navigation bar. ❓
• 🆕 Fixed some spacing issues that were affecting certain Landing Pages. 👾

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]!

Hello and welcome to another weekly update friends! Spooky season continues for yet another week with ongoing metrics updates (stay tuned!), API reference improvements, and various fixes. Details below! 🍁

👍

We've been rolling out a redesigned docs experience for some time now—check out this page for the details! Changes that are only applicable to the redesigned docs experience will be prefixed with a 🆕 emoji. The legacy docs style will be deprecated on December 31, 2021.

✨ New & Improved

• As alluded to last week, we're working on some exciting updates to the metrics experience! This release includes a lot of behind-the-scenes work so it's ready for primetime. If you'd like to receive beta access (the changes are only in the dashboard, so it won't affect your end users at all), feel free to get in touch! 📊
• This release includes a couple improvements for API Reference docs written using our Manual API Editor. Response examples now properly display the titles you set for them (🆕) and the auto-generated OpenAPI file should play more nicely with your friendly neighborhood validator. 🤝

🛠 Fixes & Updates

• 🆕 Fixed various issues around how we persist API authentication credentials between pages in the reference section. 🔑
• Fixed an issue where a select few Slack notification messages weren't being delivered. 📫
• Some minor fixes to our permissions logic for Enterprise Groups. 🔒
• 🆕 Fixed some spacing issues in the version dropdown. 🛰

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]!

Hello and welcome to another Owlet Weekly Update, folks! In preparation for this year's spooky season, we're rolling out some aesthetic tweaks and getting ready for a larger feature update coming soon. Read on for more details below! 🚄

👍

We've been rolling out some new docs designs for a little while now—check out this page for the details! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.

✨ New & Improved

• You might notice the dash sidebar has been touched up a little. These changes are coming in tandem with a larger metrics-related update we're busy getting ready for you! We've begun an internal rollout of this new feature, and if you're interested in getting involved with the beta coming soon, feel free to get in touch. 📊
• If you're feeling thirsty today, you're in luck--we've added support for generating PHP snippets that use Guzzle! Or if you're feeling a different kind of thirst, October (and most other months) is a great time to stay hydrated! 🚰

🛠 Fixes & Updates

• We're feeling great about our new API Reference experience, and we want everyone to join us in the fun! To that end, we'll be deprecating the legacy design on December 31, 2021. If you haven't made the switch just yet, check out the banner in your dash to see the preview and enable the new design! ✨
• We've made lots of stability improvements to snippet generation--query params will now always be encoded in snippets, extra headers have been removed, cookies are actually being used, and much more! You should feel empowered to get out there and continue generating as many snippets as you need! ✂️
• Some minor alignment fixes for enterprise sidebars, simplified pagination styling, and other aesthetic updates 👗
• A small update to make sure links to hidden reference pages in certain scenarios always work! 🔗

Thanks for reading and for being a part of the ReadMe community, folks!

—Naomi 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]!

Hello and welcome to another Owlet Weekly Update, dear reader! This week we're celebrating ReadMe's birthday and remain focused on some bigger projects while shipping various fixes to our Slack integration, Recipes, and more. Details below! 🎂

👍

We've been rolling out some new docs designs for a little while now—check out this page for the details! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.

📘

We ended up re-publishing this post under a new URL to reflect some additional changes that went out early Friday morning PDT. Apologies for any confusion!

✨ New & Improved

• Much like my current motivation to empty clean dishes from the dishwasher, connections to our Slack integration would mysteriously disappear. While there's no software that an engineer could write that will address my current personal crisis, this release includes several behind-the-scenes improvements to our Slack integration to use Slack's current guidance on authenticating with your Slack workspace and to prevent the mysterious disappearances. 🍽
• 🆕 This release includes a few subtle tweaks to the page markup which should help with accessibility, performance, and security. 💡
• Better handling of bigger user data payloads. 🪣

🛠 Fixes & Updates

• This release addresses a few Recipes-related bugs. The first is an issue where certain internal documentation links within Recipe steps were broken. The second is a minor styling issue where, in certain instances, the embeddable Recipes tiles weren't floaty enough. Happy to report that these links should take you to the right place and that the floatiness has ascended to normal levels. 🎈
• 🆕 Fixed an issue where users were unable to add comments to discussion posts on projects with reCAPTCHA enabled.
• Fixed an issue where certain Suggested Edits weren't rendering properly in the dashboard. 📝
• 🆕 Fixed a few quirks with the routing behavior on enterprise projects with custom child path names. 🧭
• Fixed an issue where variables weren't rendering in certain parts of the Changelog. 📛

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]!

Hello and welcome to another weekly update, friends! While we remain mostly heads down on some bigger features, this week we're shipping a few bug fixes and poppin' tags*. Details below! 💸

👍

We've been rolling out some new docs designs for a little while now—check out this page for the details! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.

✨ New & Improved

• 🆕 Tag, you're it! Just kidding. You're not "it". But you know who is? Your users when they view your API Reference docs, now that we've shipped drastically improved support for Tag Objects as part of this release! Now, if your OpenAPI file contains description and/or externalDocs properties, we now display them in a cute lil' tag icon to the right of the title. See below for an example! 🏷

🛠 Fixes & Updates

• Fixed an issue where users were having trouble embedding Recipes on certain Custom Pages. 🍽️
• Minor accessibility improvements with the Previous/Next navigational buttons. 🔙
• Fixed some tiny quirks with project ownership transfers. 🤝

Thanks for reading and for being a part of the ReadMe community, folks!

—Kanad and the ReadMe Team

*DISCLAIMER: This pun is in NO WAY an endorsement of Macklemore, nor is it an endorsement of his music. Additionally, we actively reject the results of the 2014 Grammy Awards.

📘

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]!

Hello and welcome to another Owlet Weekly Update, folks! A bit of a smaller update this week as we're mostly heads down on some bigger features coming your way in the coming weeks. In the meantime, trying out a new deployment cadence, engaging in some riveting best-food-on-a-stick discourse, and fixing a few bugs. More below! 🎙️

📘

New Deployment Schedule

This week was the debut of our two-deployment-per-week schedule (Tuesdays and Thursdays) as opposed to our typical once-a-week-on-Tuesday-and-sometimes-a-different-day schedule. The goal is to ship code faster and in smaller, less disruptive releases. 🚀

The plan is to write a single Owlet Weekly Update per week which goes over everything that went out in both of the weekly releases. We appreciate you sticking with us as we workshop a new process. Stay tuned for updates as this process continues to evolve!

👍

We've been rolling out some new docs designs for a little while now—check out this page for the latest details on what's going on! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.

📆 Upcoming (and Past) Events

• We wrapped up a super fun and informative chat with Shaun VanWeelden, Head of Field Engineering at Scale AI! The conversation wandered from sharing our Midwest state fair experiences to scaling out a documentation process across a growing organization, and everything in between (well, not everything, because those are completely unrelated). If you RSVP'd, you can check out the the event page for a recording! 🎡

✨ New & Improved

• 🆕 Made a few small copy updates to the page pagination controls so they make more sense and a global .rm-Pagination class (see our docs to see all of the available global classes!) so they're easier to customize. ⏪

🛠 Fixes & Updates

• Fixed an authentication redirect issue affecting certain Enterprise projects where attempting to suggest an edit would take you to the wrong place. 🔐
• 🆕 Fixed an issue where certain projects were experiencing issues adding votes and comments to Discussion Forums. 💬
• 🆕 Better handling in the API Reference section for endpoints with empty content objects in the response. 📭
• Fixed a minor redirect bug with localization. 🌎

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]!

Hello and welcome to another weekly update, folks! In honor of Beyoncé, we're shipping design refreshes and fixing bugs. Details below! 🐝

👍

We've been rolling out some new docs designs for a little while now—check out this page for the latest details on what's going on! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.

📆 Upcoming Events

• Next week, I'll be hosting a Q&A with Shaun VanWeelden, Head of Field Engineering at Scale AI! Scale is one of our fastest growing customers (and I gotta say, they have absolutely incredible docs), so I'm excited to chat with Shaun about favorite foods on a stick, how Scale leverages ReadMe in supporting success on their platform, and more. You can submit a question and RSVP (if you can't make it live, we'll send you a recording of the conversation) on the event page! 💬

✨ New & Improved

• 🆕 This release includes a highly anticipated rewrite of Discussions! While all the functionality and features remain unchanged, everything has been redesigned from the ground up to be in-step with the design improvements we've been making throughout the hubs. With that also comes tons of under-the-hood performance improvements to make page loading and navigation lightning fast. And perhaps most notably, we said goodbye to Josh Smith in the anonymous form placeholder and hello to Beyoncé Knowles. 👑
• 🆕 Still on the fence about upgrading your project to the latest and greatest? We totally understand! Now when navigating to your project in the dashboard, you'll see an option to set up some time with Ehsan, our incredible Product Specialist, to get some help with the upgrade process. 🤝
• As part of some broader changes coming to the dashboard in the not-too-distant future, this release includes icon updates and an overall design refresh in the enterprise dashboard. 🍥

🛠 Fixes & Updates

• 🆕 Certain projects with disabled reference sections were dealing with a quirk where the reference sections were not found, but weren't properly displaying the 404 page and were instead yielding a blank page. Not only was this a weird and confusing user experience, but this would also cause Tim Berners-Lee to weep profusely without warning. This release stops Sir Berners-Lee's crying (about this, at least) and brings back the 404 page in these circumstances. 🥲
• 🆕 This release includes some goodies for you JSON Schema fiends! We've tweaked our handling of the additionalProperties field to overcome a limitation of JSON Schema: if you're attempting to combine fields from multiple objects via an $allOf but have additionalProperties set to false, we now combine them, rather than not rendering anything in the form at all. See this page for examples! 🫒
• 🆕 You know that feeling when you unwrap a gift and it’s way less exciting than you were hoping for? This one is y’all—on certain Landing Pages, documentation categories with four (and exactly four) pages had a "View More" link after the first three pages when, in fact, we could have just… shown you the fourth page. Welp. Thankfully, this release should quell the disappointment. 🎁
• 🆕 General design improvements to various input and select components throughout our product, most visibly a change that fixes an issue where mobile-width pages were doing this awkward slight zoom thing when tapping the page selector in the guides and API Reference sections. 💅
• 🆕 Much like Steve Wozniak on Dancing with the Stars, footer notification bars in the hubs were making appearances when they shouldn't be. While we can't erase DWTS history, this release includes a fix for those notification bars. 🕺
• 🆕 Various fixes so the response schemas and examples in the API Reference section play nicely with non-JSON media types. 🤝
• 🆕 Fixed an issue where configuring a binary data format with a default Data URL would occasionally crash the page. 🗃
• Fixed an issue where child projects were occasionally out of order in the dropdown on Enterprise Global Landing Pages. 🔀
• 🆕 Tiny color fixes in various places. 🌈

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]!

Hello and welcome to another weekly update, friends! While we're not too busy mourning the end of August, we're shipping a new font in the dashboard, making little fixes and improvements in all kinds of obscure places, and writing some docs. Oh, and we're also hosting a virtual event or two. Details below! 🌉

👍

We've been rolling out some new docs designs for a little while now—check out this page for the latest details on what's going on! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.

📆 Upcoming Events

Oh hey, what's this? An events section? Not sure if this will be a permanent addition to the Owlet Weekly Update, but we have a few virtual events coming up that we wanted to make sure our dedicated Owlet Weekly Update readers don't miss out on!

• In a couple weeks, I'll be hosting a Q&A with Shaun VanWeelden, Head of Field Engineering at Scale AI (and a fellow Midwesterner)! Scale is one of our fastest growing customers (and I gotta say, they have absolutely incredible docs), so I'm excited to chat with Shaun about how Scale leverages ReadMe in supporting success on their platform, thoughtful developer experience, and more. You can submit a question and RSVP (if you can't make it live, we'll send you a recording of the conversation) on the event page! 💬
• In the hopefully not-too-distant future, I'll be live-streaming as I build a website using a public bus-tracking API. It should be a fun time as I drift into unfamiliar territory with some not-so-great API docs and an even worse Twitch streaming setup. Watch this space for details! 🚍

✨ New & Improved

• Now this one isn't a product update, but we recently added a wonderful resource to our documentation—a comprehensive OpenAPI Compatibility Chart! This page goes deep on the OpenAPI Specification and which aspects of it that we support in our API Reference documentation. We'll be updating this page as we ship new OpenAPI features, so definitely keep checking back as we continuously invest in our OpenAPI support (and stay tuned for more on this front)! 📚
• 🆕 This release considerably enhances the way we document various format values for integer and number data types in the API Reference section. We now display the integer maximum and minimum values based on their formats (e.g. an int8 will render minimum and maximum values of -128 and 127, respectively). To see an example of this in action, check out these docs and navigate to the "format data types" page (listed under the Numbers category). 🔢
• This release includes a small but mighty update to our dashboard design—in the form of a new font! This comes ahead of some big changes coming to the dashboard soon—stay tuned! 🎨

🛠 Fixes & Updates

• 🆕 Various fixes to authentication in the API Reference section so authentication credentials are better persisted when switching endpoints, along with improvements to zero-config metrics on the whole "knowing you who actually are" front. 🔐
• 🆕 Fixed an issue where, under an extremely obscure and specific set of circumstances, page body content in the Guides section wasn't properly updating when navigating between pages. 🔄
• 🆕 Various improvements for api-generated code snippets—including minor padding fixes for multi-schemas (i.e. anyOf, oneOf) and the dramatic return of form-encoded parameters. 📝
• 🆕 Fixed an issue in the API Reference section where, if a request example was selected, editing parameter values in the form wasn't properly updating the code snippet. ✍️
• 🆕 Fixes two obscure and unrelated markdown rendering issues in the response schema modal in the API Reference section and in the top navigation bar. 👀
• 🆕 This release includes updates to our discriminator mapping support—support for schema reuse in mappings and various minor bug fixes. 🗺
• 🆕 Fixed a quirk in the Changelog where extremely long code samples were causing the page to break. See below for an example! 🤥
  JavaScript

  console.log("Hello there! It's been some time since we've embedded a code block directly in the Changelog. As you can see, the overflow on this obscenely long code sample is properly being handled and isn't breaking the page! Love that.

• 🆕 Did some minor shuffling around in the navigation bar so child project + version selection makes a little more sense. 🧭
• 🆕 Stability fixes in the API Reference to better handle duplicate enum values. 👯‍♀️
• Fixed an issue where certain emojis weren't properly rendering callouts. 👍
• 🆕 Tiny tweaks to prettify certain JSON response code samples. 💋
• 🆕 Various layout and design fixes in Suggested Edits. 📐

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]!

Hello and happy Virgo season, friends! This release includes certain touch-ups with an attention to detail that only a quadruple Virgo could have, as well as several other improvements and fixes that I struggled to tie to Virgo season. More below! ♍

👍

We've been rolling out some new docs designs for a little while now—check out this page for the latest details on what's going on! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.

✨ New & Improved

• 🆕 This release includes various improvements on the performance and stability fronts for certain API Reference sections. Thanks to a few minor changes to how we handle JSON Schema, certain circular $ref parameters that previously weren't rendering should now render as expected and lots of projects will experience a small performance bump as a result! 🚀
• 🆕 This release includes a major redesign to the API Logs page in the Hub to reflect our new design system and architecture! It's now sleeker and far more performant. ⚡
• 🆕 Tweaked the spacing and color contrast on the schema form in the API reference section to help improve readability, particularly for complex schemas. 🖌️
• Minor performance improvements when querying page view data from certain places in the dashboard. 🎑

🛠 Fixes & Updates

• Growing up, you probably heard a gendered variation of the phrase "like parent, like child". As many of us have learned over time (both in life and with respect to documentation architecture in ReadMe), that often isn't the case! But we don't have time to unpack all of that. This release improves the reliability of the workflow of hiding a parent page—it now properly hides all of its children pages and hides them from your search results. 👪
• 🆕 As you may know, the redesigned reference docs include better support for readOnly and writeOnly parameters and examples. Unfortunately we were seeing an issue where certain readOnly/writeOnly parameters weren't rendering examples if they were located within certain allOf schemas. Thankfully, this release includes a fix that brings them back. 🤓
• Fixed an issue where certain projects weren't counting zero-configuration API Metrics in their total API log counts. 📈
• 🆕 Loosened our requirements for valid security schemes. 🔐

As always, thanks for reading 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 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]!

It's that time of the week again, folks! You know that fancy form in the API reference section? The one where you can enter parameter values when constructing an API request? Well as you may know by now, we massively redesigned it in the last few months to include better support for example parameters, nested objects, and lots of other good stuff. Well the good stuff continues with this release—fancy tooltip schema validation, user-specific parameter defaults, and much more. Details below! 🥭

👍

We've been rolling out some new docs designs for a little while now—check out this page for the latest details on what's going on! Changes that are only applicable to the new docs design will be prefixed with a 🆕 emoji.

✨ New & Improved

• 🆕 You may have seen "fancy tooltip schema validation" mentioned above... but what exactly does that mean? Now, your docs will determine the schema for each form field based on your API specification and provide instant visual feedback to the user as they enter data to make sure they're adhering to your data requirements. Oh, and did we mention that this is all in fancy tooltip form? Not to toot our own horn, but our docs are a great way to see this in action. ✅
• 🆕 Now let's be honest—adding parameter defaults in your docs can be great! Saves a potential click and provides helpful context for your users. But sometimes a one-size-fits-all approach isn't good enough. Well as of this release, you can take that personalized documentation experience to the next level and pass in parameter defaults via the user data payload. Check out our docs for the details. 📛
• 🆕 Subtle design and animation improvements to certain buttons and dropdowns throughout the product. 🎨

🛠 Fixes & Updates

• 🆕 This release includes several improvements to the sidebar, primarily with respect to accessibility! Now it's easier to navigate the sidebar via a keyboard, with better support for parent/child page toggling and better visual cues. It also includes several small stability improvements for a select few pages so selecting a link from the sidebar actually takes you to the right place. 🧭
• Now here's a cute ReadMe fact: when you submit a Suggested Edit and the project administrators approve it, you get an email commemorating your generous contribution of knowledge! But the celebration was occasionally ruined when the link to the updated page would lead to the wrong page. This release includes a fix that should keep the party going. 🥳
• 🆕 Light text on a dark background? Great. Dark text on a light background? Love it. Light text on a light background? Yikes. For users on certain mobile devices, this release addresses the last category for certain navigational dropdowns. 📱
• 🆕 This release makes it so the API Reference section does a better job of displaying HTTP codes when a user clicks the trusty "Try It" button for certain API configurations. 🟢
• Fixed an issue where certain project admins were unable to directly save edits via the Suggested Edits view. 💾
• Fixed an issue where a select few unlucky users were unable to easily navigate back or forward in the dashboard. 🔙
• Fixed a couple of edge cases when re-saving API definitions via the manual API editor. 🔄
• 🆕 Minor stability improvements for response examples. 🐴

As always, thanks for reading 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 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]!