Discussions

Hi there, Currently admins for API are logged in via email. If we add Custom Login Flow will admins still be able to login via emails? Or should we add admin/user roles to custom login callback JWT?

What is the markdown required to emulate what you get when using the Code Sample widget? I found [your documentation](https://rdmd.readme.io/docs/code-blocks) on how to write the markdown for a tabbed code block with a title in each tab, but I don't need two interactive tabs, just the visual look of two tabs so that the language type is displayed in tab A. In other words, exactly what you get when you use the widget. I tried viewing an existing page in raw mode, but the language specification seems to be bundled in with the code sample. ``` [block:code] { "codes": [ { "code": "{\n \"result\": [\n {\n \"order_id\": 488,\n \"status\": \"active\",\n \"user\": \"\",\n \"sell\": {\n \"type\": \"ERC721\",\n \"data\": {\n \"id\": \"\",\n \"token_address\": \"\",\n \"quantity\": \"1\",\n \"properties\": {\n \"name\": \"\",\n \"image_url\": \"\",\n \"collection\": {\n \"name\": \"Gods Unchained\",\n \"icon_url\": null\n }\n }\n }\n },\n \"buy\": {\n \"type\": \"ETH\",\n \"data\": {\n \"decimals\": 18,\n \"quantity\": \"1200000000000000\"\n }\n },\n \"fees\": [\n {\n \"type\": \"royalty\",\n \"address\": \"\",\n \"amount\": \"200000000000000\",\n \"token\": {\n \"type\": \"ETH/ERC20\",\n \"data\": {\n \"decimals\": 18,\n \"contract_address\": \"\"\n }\n }\n }\n ],\n \"amount_sold\": null,\n \"expiration_timestamp\": \"2120-08-25T04:00:00Z\",\n \"timestamp\": \"2021-08-25T04:33:19.85441Z\",\n \"updated_timestamp\": \"2021-08-25T04:33:19.85441Z\"\n }\n ],\n \"cursor\": \"...\",\n \"remaining\": 0\n}", "language": "javascript" } ] } [/block] ```

I wonder is it possible to enable some sort of authentication to the site that is generated by readme? I would like to hide the api information from public user and only show it to some internall group.

What is the suggested workflow in Readme for SMEs to review and comment on both published and unpublished content?

Hi When i try to import a swagger file , i am gettign the below error: ``` Swagger schema validation failed. ADDITIONAL PROPERTY must NOT have additional properties 307 | "type": "number" 308 | }, > 309 | "format": "double", | ^^^^^^^^ 😲 format is not expected to be here! 310 | "allowEmptyValue": false 311 | }, 312 | { ```

How to configure the API Reference section to show Bearer Token input field? Noting that I am not using OpenAPI, as I am building the reference section manually from the website (dash.readme) 

<https://swagger.io/docs/specification/api-host-and-base-path/> see section "Overriding Servers" This doesn't seems to work in readme. However it is supported in Swagger. Is this somewhere planned?

Hi, I have a table overflow issue: https://docs.rejoiner.com/docs/template-tags#viewed-items--global-product-data But, I can't add custom CSS to correct it. Is this something that could be addressed by default?

Hello all, I am creating a page for a (bit complex) data model, and the table breaks the size of the page: https://docs.tokeny.com/docs/onchainid-standard-schema#config (scroll to the bottom of the page) Is there a way to fix it easily? Thanks a lot

Firstly, I'm confused by your conflicting instructions. On the glossary management page in my account (/v1.0/glossary-definitions), the page description reads: "To use, type <<glossary:phrase>> in your documentation" It doesn't say anything about case sensitivity, so I was surprised to discover recently that when a term entered as "Withdrawal" is referenced in a doc as <<glossary:withdrawal>>, it is omitted from the customer view of the page. Then I came across this example [in the documentation](https://rdmd.readme.io/docs/features#glossary-terms): Both **GLOSSARY:EXOGENOUS** and **GLOSSARY:ENDOGENOUS** are long words. Which displays the words in lowercase. Great! However, when I tried that myself, using **GLOSSARY:MAINNET** in a doc, in the hope of it retrieving my definition for <<glossary:mainnet>>, it shows up as: "The functionality described on this page is not yet available on GLOSSARY:MAINNET." Do I have to create duplicate glossary entries to accommodate both upper and lowercase usage of the term?