Hello and happy Triple Aries szn, y'all! We're continuing work on our editor (with its beta right around the corner!), making big updates to our reference preview site, and fixing a whole bevy of bugs. More below! ♈

✨ New & Improved

  • We’ve made some quality-of-life improvements to our reference preview site! We added dozens of example OpenAPI definitions that you can preview in our API Reference section. You can also load in your own OpenAPI definitions as well! 🍿
  • We’re in the process of rolling out our new Enterprise Authentication experience! This release includes more work on that front. Get the details on everything here! 🔑
  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️

🛠 Fixes & Updates

  • We’ve got good news for users of APIs using Basic Authentication—we fixed an issue that was dropping your credentials as you navigated around the docs. 🍪
  • Fixed some crashing issues affecting API Reference pages that contained certain kinds of array/object parameters. 💥
  • Fixed an issue where certain Operation IDs were causing links to break on subsequent re-syncs. 🔗
  • Fixed some readability issues affecting the search modal on certain projects. 🔍

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

—Kanad and the ReadMe team :owlbert:

📘

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, y'all! This week we're making some improvements to our JSON Schema handling, fixing a few bugs, and continuing work on some exciting projects. Details below! 🍌

✨ New & Improved

  • Per the OpenAPI v3.1 specification, including summary or description values alongside a $ref pointer should override those respective values of the referenced component. This release includes an update to our JSON Schema handling in the API Reference so we respect that override! 🎡
  • We’re in the process of rolling out our new Enterprise Authentication experience! This release includes more work on that front. Get the details on everything here! 🔑
  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️

🛠 Fixes & Updates

  • Fixed an issue where malformed operationId values would cause certain API reference endpoint pages to crash. 💥
  • Various styling fixes in the API Reference. 💅
  • Minor security fixes. 🔐

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

—Kanad and the ReadMe team :owlbert:

📘

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

Happy April Fools Day y'all! We're celebrating by unironically doing a huge launch. 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

  • We spent the last few months completely redesigning our homepage from the ground up and decided to unironically launch it today (April 1st)! While April Fools Day is a questionable day to announce big website redesigns, we were too excited to wait until Monday. Be sure to check out the new digs! 🏡
  • We’re in the process of rolling out our new Enterprise Authentication experience! This release includes more work on that front. Get the details on everything here! 🔑
  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️

🛠 Fixes & Updates

  • Fixed an issue in the API Reference where clicking between API logs would drop your Authorization header at some point in the process. 🗝️
  • Turns out, our PUT /api-specification endpoint wasn’t properly surfacing certain validation errors, so this release fixes that. 🚧
  • This release fixes an issue for Safari users where clicking the “Try It!” button in the API Reference would periodically crash. 🧭
  • Various styling fixes across the board. 🎨

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

—Kanad and the ReadMe team :owlbert:

📘

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 Aries season, y'all! Lots of little improvements and bug fixes were released this week. 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

  • We’ve added the a setting in the dashboard for enabling includeSubDomains parameter for the HSTS response header. You can configure this in the same place you configure your custom domain. 🌐
  • We’re in the process of rolling out our new Enterprise Authentication experience! This release includes more work on that front. Get the details on everything here! 🔑
  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️
  • Added a new global CSS class for the “Log In” button in the top-right corner of the hubs. 🎨

🛠 Fixes & Updates

  • We’ve received some feedback that the page voting thumbs can be a bit confusing to interact with, so this release includes improvements on that front. Feel free to check out a demo of the improved behavior in our docs! And if you found the page helpful and/or you’re looking to play with the new behavior yourself, maybe give the page a thumbs-up? 👍
  • There’s a setting to hide the Table of Contents, but the API Reference has continued to exist on a chaotic plane and in complete disregard of this setting. This release brings the API Reference back down to earth. 🌏
  • For Enterprise projects with lots of child projects (we’re talking over twenty projects), this release includes improvements to the search modal so it can better filter for content across all your projects. 🔍
  • Made a few improvements to our security scheme processing logic in the API Reference so hitting the “Try It!” button will work, even if the security scheme is incorrectly defined. 🔒
  • Fixed an issue where certain email notifications for Suggested Edits included broken links. 🔗
  • Fixed some server-matching issues when populating endpoints for Metrics. 📈
  • This release includes even more fixes to Page History for Custom Pages. ⌛

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

—Kanad and the ReadMe team :owlbert:

📘

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! We continue to recycle pop culture references and remain heads down on some big upcoming projects, but in the meantime we're shipping a new API endpoint and rolling out our new Enterprise Authentication experience. 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

  • For some time now, we’ve had an endpoint in the ReadMe API so you can programmatically apply for a job with us. We’ve made some behind-the-scenes improvements to that endpoint, along with an in-front-of-the-scenes improvement in the form of a new endpoint for retrieving all of our open roles! You can find the new endpoint documentation here. 📮
  • Building off our API Reference support for callback objects and the deprecated keyword comes support for... deprecated callbacks! Now, when the callback object’s inner Operation object has the deprecated field set to true, we’ll properly surface that information to the user. 🍌
  • We’re in the process of rolling out our new Enterprise Authentication experience! This release includes more work on that front. Get the details on everything here! 🔑
  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️
  • General styling and language improvements in our API reference documentation. ✏️
  • Small accessibility improvements for mobile users. 📱

🛠 Fixes & Updates

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

—Kanad and the ReadMe team :owlbert:

📘

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

🚧

This is a Staged Rollout!

We're rolling out this new experience to current Enterprise customers over the next few weeks to ensure a smooth transition. You'll get an Intercom notification in your dashboard when the functionality is live for your group. If you have any questions don't hesitate to reach out directly to your Product Experience Manager!

Making sure all of your team members and customers have the permissions to properly access your ReadMe docs? That's a... (ahem) major key to success*, folks. 🔑

When it comes to managing your Enterprise Group, there can be a lot of moving parts—multiple projects to oversee, lots of eyes on various parts of your docs, and team members and customers requiring different permission levels depending on how they need to interact with your projects. While we love the idea of you sharing your docs with the world, we want to make that sharing experience one that instills confidence rather than confusion. You’ve put enough energy into making your docs beautiful, personalized, and interactive, let us take care of making sure that you can manage your ReadMe projects and teams with ease.

On that note, over the last year we’ve been tinkering away at making our Enterprise authentication and access management experiences more intuitive, and well, better 😎 We're excited to share that these features are now…lights, camera, actionLIVE for all Enterprise customers! ✨

The Scoop 🍨

First, the sidebar in your Enterprise Group dashboard is looking a little different 🧐 We heard from our Enterprise Group Admins that it’s challenging to manage permission settings, especially when managing multiple projects within an Enterprise Group. We also got feedback that bulk inviting individuals to projects, whether they were technical writers needing to access some but not all project dashboards, or customers who needed hub-side access to private docs, was cumbersome and frustrating at times. So we set out to upgrade all of that.

To make it easier to distinguish between user roles, the former, unified Members page in your dashboard is now two separate sections: (1) Teammates and (2) End Users.

Teammates are members of your team who manage (e.g. write, edit, update) documentation related to your projects. End Users are consumers of your projects’ documentation whom you’d like to grant hub-side only access to.

Teammates and End Users have unique needs, and now we’ve created more distinct user permission settings that better map to how you want your team members and customers to interact with your docs. For both of these new user roles we’ve simplified the login configuration and added increased functionalities around managing login methods, access privileges, and default user permissions. This distinction also allows us to keep building more secure and user-friendly docs for both user functions 👍

For some of our Enterprise Admins, it was a headache to manually manage Read Only and Admin permission levels for dozens of users across dozens of projects. So to allow for easier team and multi-project management at scale, the new End User Management page simplifies the process of bulk inviting users to projects and more clearly delineates what projects End Users have access to.

There’s also a new Projects page that makes it easier for Enterprise Group Admins to manage multiple projects at the group level. In this page you can see what projects are associated with an Enterprise Group, as well as add, remove, and/or make projects public or private.

Ray from our team recorded this live walk-through to highlight the new updates we’ve made 📹

And here’s a li'l breakdown of everything that’s changed:

NEW FeaturesImprovements + Updates
Teammates Page with new settings:
- What’s it all about: where to configure access and invite users from your team (e.g. your company)
- The Domain Safelist dropdown allows you to set a domain and allow anyone with an email address at that domain to create a ReadMe account
- Login and authentication configurations including SSO dropdown + enforcement settings allowing Enterprise Group Admins to determine how they want Teammates to sign in to ReadMe
- Default permission level settings for new invited Teammates
- A new method for inviting teammates and assigning permission levels, as well as new permission levels to choose from (Group Admin, Group Viewer, Custom)

New End Users pages:
- (1) End User Login page with ability to configure the login method for your private docs (hub-side access)
- (2) End User Management page with ability to see and filter users that have access, and bulk invite new users

Projects Page to manage multiple projects within an Enterprise Group
- The Manage Projects button allows Group Admins to add or remove projects
- See all child projects in one centralized place and set as Public or Private
- Unified view for user permissions
- Clearer visibility into users’ roles
- Ability to filter Teammates by permission level and project access
- Redesigned UI for seeing private vs. public projects
- One consolidated UI for configuring hub-side login access

You can read more about this new experience in this overview guide. We hope you’re excited for these updates! We’d love to hear from you, whether to share your feedback, ask a question, or just say hello. Feel free to click the Intercom widget to leave a message or send a note to [email protected] :owlbert:

*What's a long-form piece of content on authentication without a DJ Khaled reference?

Hello and welcome to our first full week of March, friends! This week, we're shipping v7.0.0 of rdme, syntax highlighting support for an additional language, and an owl fact. More 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

🛠 Fixes & Updates

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

—Kanad and the ReadMe team :owlbert:

📘

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! We're making headway on some big projects and making some big improvements to our GitHub Actions support. 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

  • We’ve added first-class GitHub Actions support to our good friend rdme: ReadMe’s official CLI (and as of this week, GitHub Action)! You can sync OpenAPI definitions, you can perform pre-upload OpenAPI validation, and even sync directories of Markdown files—all within an automated GitHub workflow. As part of this, we’ve officially parted ways with our legacy GitHub Action. Check out our new docs page (which, I should add, is synced from the rdme GitHub repo using the rdme GitHub Action) to get the details! 🔄
  • 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 we’ve begun rolling this out to Enterprise projects! This release includes even more work on this front. 👥
  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️

🛠 Fixes & Updates

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

—Kanad and the ReadMe team :owlbert:

📘

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! We had a short week due to a company holiday and we're heads down on a few exciting upcoming projects (stay tuned!), but just know that we finally fixed a bug that I identified the corresponding pop culture reference for weeks ago. More 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

  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️

🛠 Fixes & Updates

  • Although Damon was completely wrong about Taylor, he probably would have been onto something if he was accusing ReadMe documentation writers of being miscredited for their work... because that was the case, at least for a little bit! For a short period of time, our Page History records were incorrectly always attributing the author of the edits to the person who created the page. While we’re unable to do anything about Mr. Albarn’s Twitter ratio, this release includes a fix so page history going forward should reflect the correct songwri—I mean, author. 🦍

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

—Kanad and the ReadMe team :owlbert:

📘

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

Happy Week of Valentines Day, y'all! Seeing as our collective love languages are acts of service and words of affirmation*, this release delivers just that. More 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 we’ve begun rolling this out to Enterprise projects! This release includes even more work on this front. 👥
  • This release adds some much-anticipated endpoints to the ReadMe API: you can now create, edit, and delete categories via our API! It wouldn’t be a ReadMe API announcement without a link to our endpoint docs, so be sure to check those endpoints out here! 🗄️
  • This release includes even more improvements to our soon-to-be-released editor, which you can get a sneak peek of in our discussion forums! ✍️
  • Minor accessibility improvements in the search results, which should make it easier to open results in a new tab. 🔍

🛠 Fixes & Updates

  • We’d like to give a quick shout out to the response sections in the API Reference that refuse to conform to the societal norm of numerically sorting their response codes. 200s, followed by 500s, followed by... 400s?! This is bold and brave stuff, y'all. We see you and we appreciate you! And we fixed an edge case where your response titles were getting a little mixed up. 🔀
  • Fixed a few enterprise-related quirks that caused our Slack integration to not send messages in certain circumstances. 📥
  • This release fixes some long-standing issues with PDF generation. 📝
  • Fixed a couple quirks with the creation of Recipes. 🧑‍🍳

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

—Kanad and the ReadMe Team :owlbert:

*(and probably all of them, in some capacity)

📘

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