> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/community/contributing-to-tsg-forge-wiki/folder-template/discord-message-article-template.md). # Discord Message Article Template If you want to submit content to the TSG Forge Wiki, but would prefer to just be able to write down information with a very low level of entry and still see it published on the wiki, you can write an article with good formatting within a discord message or text file and post it on the [Wiki Discussion](https://discord.com/channels/220766496635224065/1032391999740969011) forum on the TSG Discord server. {% embed url="" %} It will then be evaluated and published on the wiki by a volunteer wiki moderator. Keep in mind that as this process is more complex than merging [pull requests](/community/contributing-to-tsg-forge-wiki/submitting-content-to-the-wiki.md#submitting-a-pull-request), it will take longer for wiki moderators to get the content to the wiki. In order to make the process as smooth for both parties, we've created this message template that should be used for these Discord forum posts.
Discord icon on a grid
## Message template This message template should be copied into a text editor where it is worked on until it's ready to submit to the [Wiki Discussion](https://discord.com/channels/220766496635224065/1032391999740969011) forum. ````markdown # Article Topic Here ``` Shortly describe the topic in this description field and what the main purpose of the thing being discussed is. ``` Give a brief explanation of the topic that the article is about. What is the purpose of the thing and what kind of adjustments can be done to it. Keep it short, as the sections below should be used for further explanation. [Cover image] Temporary section for general notes about the article; write down things quickly that you want to write about so you can easily recall them later. Delete this section when the article is finished: * * * ## First heading 1 title Write about a branch of the main topic. This section title will show up on the sidebar on the right. ### Sub-heading 2 title Write about a sub-section of the topic above. This section title will show up on the sidebar on the right. [image1] [image2] More text here about the topic. **Sub-heading 3 title** Write about an even more specific topic of the sub-topic above. This section title will _not_ show up on the sidebar on the right. ## Second heading 1 title Write about another branch of the main topic. ```` This formatting is not 100% identical to the formatting on a wiki article as Discord displays some of the Markdown formatting differently, but it's close enough where wiki moderators can easily copy and paste the text to the relevant fields for a wiki article. Discord Markdown formatting doesn't display an "h4" title (`#### Title name`) so it's substituted with bolded (`**Title Name**`) formatting instead. It should be stated after the article which images correspond to which `[image]` fields in the message so there's less figuring out for the wiki moderators on where to position the images. ### Information not worthy of a full article For information that doesn't need it's own article and could instead be added to an existing article as a sub-section, the same message template can be used, but with a few modifications. Instead of submitting a message or text file with the entire message template, you can cut out the information before your sub-section and submit it like that. Just be sure to mention to which article it would be an addition to. So for example your submission could start at: ```markdown ## Second heading 1 title Write about another branch of the main topic. ``` *** #### Contributors Okom --- # 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://wiki.thescriptersguild.com/community/contributing-to-tsg-forge-wiki/folder-template/discord-message-article-template.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.