> For the complete documentation index, see [llms.txt](https://docs.wavecast.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wavecast.io/publishing/create-content/creating-an-article.md). # Creating an Article ### Getting started From the sidebar menu, click **Content**, then select **+ Create Content > Create Article**. *** ### Article fields Fill in the following details: * **Title** — The article's title as it will appear on the platform. * **Excerpt** — A short summary of the article. * **Body** — The full article content. * **Reading time** — Optional. An estimated reading time for the article. * **Featured image** — A header image for the article. We recommend using a dark image, as the header copy is white. * **Permissions** — Set to **Guest**. * **Taxonomies** — Select relevant terms under **Topics** and **Companies** where applicable. *** ### Publication status The default status is **Published**. If you are not ready to publish, change the status to **Draft** before saving. Update to **Published** when you are ready to go live. *** ### Saving Click **Update Article** to save your changes. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wavecast.io/publishing/create-content/creating-an-article.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.