> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/editor.md). # Editor How to use Pylon's WYSIWG editor to write knowledge base content Pylon's knowledge base editor is a "what you see is what you get" (WYSIWG) style editor. This means your customers will see content exactly as you type it. Content is added in the form of **blocks**, which are individual elements in the article. Blocks can be dragged around to reorder them or deleted. To get started, type `/` in your knowledge editor to see what blocks are available. {% hint style="info" %} The knowledge base editor also supports markdown-style syntax. For example, you can type "#" to start a Header 1, ">" to start a blockquote, etc. {% endhint %} ## Blocks Currently supported blocks in Pylon's article editor are: * All common rich text like bolds, italics, underline, strikethrough, inline code, links, etc. * Headers, with 3 different sizes * Text justification * Numbered and bulleted lists * Accordions * Callouts, with customizable icon and color * Code blocks * Tabs with filenames and syntax highlighting in 20+ languages * Blockquotes * Native relative links to other knowledge base pages * Tables, with header rows and colored cells * Inline images, with resizing, justification options, captions, alt text, etc. options * Embedded videos, like Loom and YouTube * Embedded downloadable files * Custom embeds, like Scribe and Arcade (or any site that supports embeds) * PDFs, displayed in an inline viewer * Mermaid diagrams, such as flowcharts and sequence diagrams, written in Mermaid syntax with a live preview. Diagrams also render in the chat widget. * Custom HTML, rendered in the article * Math equations in LaTeX: wrap an expression in `$$` for inline math, or put it on its own line wrapped in `$$$` for a block equation * Emoji: type `:` followed by at least two letters to search * [Synced blocks](/pylon-docs/knowledge-base/articles-and-collections/synced-blocks.md) * Re-usable blocks with content that stays in sync across articles * Horizontal dividers * Internal notes, special content that is only visible when your team member is viewing the article While typing in a block, you can highlight text for options to edit that text's format within the block or add links. You can also press the `+` key to add a relative link to another article in your KB. --- # 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.usepylon.com/pylon-docs/knowledge-base/articles-and-collections/editor.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.