Discussions
Segment Integration sends wrong data
Hi
How do we change our name from `null` in discussions when logged in?
I understand we can edit our profile via the readme.com dashboard but this does not change the name in when posting in discussions (currently null). Anyone know how to set our default name for all README discussions?
Try now button
I have imported a OAS file which automatically enabled Try Now button for all endpoints. I understood that I can can turn it off by setting the OpenAPI extension x-explorer-enabled to false. But, with the design our documentation page will be visible to everyone, regardless logged in or not. So I am curious how to handle the case when users not signed in yet my platform so no api key can be retrieved.
Is there a workaround for supporting "anyOf" in readme?
I am working to port over our docs and we use anyOf for an object type. Does readme support that structure? if not is there a workaround?
How to provide the OpenAPI specification to the customers?
Hi, we want to share the OpenAPI specification publicly with our customers. We see that there is a public link for it("view oas"), but this link is not permanent across API versions. Could you please advise us on how to achieve what we want? The feature is much needed because some developers still prefer to import the file in Postman.
Customing Tags in OAS
Pages are created when we specify tags in our OAS, but I wanted to add more information on this page, ideally a markdown. Is there a way for us to do this via CLI?
Expanding search limitations
Are there any plans to expand the search limitations on Algolia searches? I want to use collapsible sections in my guides, but can't because of the way the search ignores content wrapped in raw HTML. I know you can assign keywords for SEO metadata, but do those keywords also come up in search results within my product guides? I'd love to not have to choose between lots of scrolling and ensuring searches return the expected results.
Performance issues - How to pass Core Web Vitals
We'd like to move to ReadMe but have concerns about performance of the ReadMe platform and failing Core Web Vitals. This is important given we need to be able to drive organic search traffic to our documentation and will be more critical in March 2024 when Google replaces FID with Interaction to Next Paint (INP).
When will ReadMe support AsyncAPI?
Our team (growing startup of ~30) wants to transition our full docs to http://readme.io, but we can't until you add AsyncAPI support. I've seen many other readme users ask for this feature as well - see other questions and other comments on multiple forums.
Uploading valid OPENAPI json file shows only endpoints on the left side
The UI is showing all the API endpoints but they are empty