We'd like to change the URL of 'Announcements' to whatever the name of that section is. In our case, the section is called Changelog, and we'd like the URL to reflect that. I don't see any options in the settings to make this kind of change, unless I'm missing something!
Posted by Trevor 3 years ago
As is, when a link is made using \[text\]\(doc:pageslug\) in an Announcement, and said link is supposed to go to a reference, 2 issues occur: 1. You are taken to the Documentation section with it's sidebar, instead of the new Reference section. 2. You are not taken to the anchored reference, instead staying at the top.
Posted by Joseph 3 years ago
We have a combination of public methods which are used by developers outside our company. We also have a number of internal methods that we use for our own functionality, but are not appropriate for 3rd party developers. Is there a way to manage both public and private documentation/methods?
Posted by Joshua Rich 3 years ago
Hi, I am trying to use the API Explorer to document my API. Every time I go to the "live" version of my reference document all the PATH PARAMS for my GET Requests appear as `required`, even when I set them to not be `required`. The changes in the API Explorer editor doesn't seem to have an effect. I would like them not to be `required`. Any idea of what could be going wrong? Best
Posted by Kristian Garza 3 years ago
Hi there! I can't figure out how to links to an anchor with an escaped underscore in its name. I tried this with no luck: This: [tvIn\_KeyboardModifierAlt](#section-tvIn-_KeyboardModifierAlt) should link to this on the same page: ### tvIn\_KeyboardModifierAlt
Posted by Achim Breidenbach 3 years ago
The Results Format section is not appearing at all even though I have multiple results documented. This appears to happen when the first result listed has no content as the result. Subsequent results will auto-fill a no content result with the text ‘no content’, no that is the expectation for the first result.
Posted by Nikolas Doukellis 3 years ago
I can see the <get> and <post> type in edit mode, but they disappear on the actual page. live: /orgs in edit: POST /orgs How can I get the request type to show up without physically writing it in heading? Is there a setting somewhere I should tweak or has something changed in readme? Thanks!
Posted by Ashley Baldwin-Hunter 3 years ago
In our current help we have 'show me how' guides within a help guide if more information is needed. We click on 'show me how' and the additional information is presented to the user on the same page rather than them having to have another page open. The 'show me how' expands and the additional text / images can be seen and the user can then close the collapse
Posted by Michelle Burdett 3 years ago
Hi! I was wondering if there was a feature on the road map to allow user's to run multipart requests with the API Explorer. If this is not possible, would it be possible to easily remove the "Try It" feature from select pages on our documentation? Thanks in advance for the help!
Posted by Raj 3 years ago
Hello. I try to replicate this layout : https://sample-default.readme.io/docs In the left column, there's an ENDPOINTS block. I don't manage to replicate this. The endpoints I defined can be seen in the "reference docs page" but I can't add the list of endpoints on my documentation page. Thanks for your help. Regards.
Posted by David Emo 3 years ago
Hi, I need to change the default font family that is monospace to Monsterrat but there ain't option in settings or appearance to do that. I believe it would have been possible to do via Custom CSS but since Monsterrat is not a default font then how do I upload it. Any clue ? Thanks
Posted by Himanshu Singh 3 years ago
I am looking for in-depth THEME edition documentation showing me exactly which options change what in my hub; preferably with video or screenshots attached. How to setup certain screens (and a place where I can preview them). Will appreciate all the help :)
Posted by Albert Palka 3 years ago
When we do Try It from the API explorer from a https enabled readme.io, we get a 404 error, but looking in the console we can see that its being blocked because it's a http request to the tryit proxy. Has anyone got a way round this?
Posted by Dj Walker-Morgan 3 years ago