> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/classic/user-manual/page-types/markdown.md). # Markdown Markdown allows you to write using an easy-to-read, easy-to-write plain text format Markdown is one of the most popular ways to write for the web. By using a lightweight and easy to read syntax you can write and edit text without having to wade through HTML. You start writing, and when previewing or publishing your Markdown pages, RapidWeaver will generate the HTML for you! ### The Basics ``` **Text contained within sets of two asterisks appears in bold** _Text with an underscore on either side area is shown in italics_ [This text will link to the Realmac Software website](http://realmacsoftware.com) ``` ### About Markdown Markdown is incredibly simple to get started with. There are also some advanced options that you can make use of - for a complete list of Markdown syntax that you can use, visit the official [Markdown documentation](https://daringfireball.net/projects/markdown/syntax). If you have a basic knowledge of Markdown, then use [this cheatsheet](https://www.markdownguide.org/cheat-sheet/) as needed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.realmacsoftware.com/classic/user-manual/page-types/markdown.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.