> Portal Navigation: > > - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version. > - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages). > - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`). > - Top-level index of all portals: https://dev.wix.com/docs/llms.txt > - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt ## Resource: Sample Flows ## Article: Sample Flows ## Article Link: https://dev.wix.com/docs/api-reference/assets/rich-content/ricos-documents/sample-flows.md ## Article Content: # Ricos Documents API: Sample Flows This article presents a possible use case and corresponding sample flows that your app can support. These flows can be a helpful starting point as you plan your implementation. ## Convert site visitor input between Ricos document and Markdown formats In this scenario, your app or site allows site visitors to create and edit content. They can choose whether to create the content using a rich content viewer or in a Markdown editor. They can toggle between the two formats while editing the content. ### When the site visitor toggles from rich content to Markdown 1. Call [Validate Document](https://dev.wix.com/docs/rest/assets/rich-content/ricos-documents/validate-document.md), specifying: - The site visitor's current Ricos document. - The plugins your rich content viewer supports. - `fixDocument` set to `true`. 1. Call [Convert from Ricos Document](https://dev.wix.com/docs/rest/assets/rich-content/ricos-documents/convert-from-ricos-document.md), specifying: - The `validDocument` value from the previous step's response. - The target format `MARKDOWN`. Use the response to populate your Markdown editor. ### When the site visitor toggles from Markdown to rich content Call [Convert to Ricos Document](https://dev.wix.com/docs/rest/assets/rich-content/ricos-documents/convert-to-ricos-document.md), specifying: - The site visitor's current Markdown content. - The plugins your rich content viewer supports. Use the response to populate your rich content editor.