This page is for those who have editor rights. If you do not, there is nothing to read: the buttons described here simply will not appear.
Rights are granted manually. If you want to help more, please write to us via the feedback form. → How to help the project
What an Editor Can Do
- write and edit articles and guides;
- create and manage presentations; → Slides and Presentations
- edit dictionary entries;
- trigger a re-analysis with a hint;
- create additional AI sections.
Separate from the editor role is the administrator — responsible for moderation, users, and batch operations.
Articles and Guides
Go to Articles → + Create.
Texts are written in Markdown
Standard markup: headings starting with ##, lists, tables, links. The page title is set in a separate field; there is no need to duplicate it in the text.
Two of our custom additions:
[[คำ]] — link to the dictionary. A Thai word in double brackets turns into a link to a dictionary entry; if the word is not in the dictionary, it becomes a link to the search. You can add a label: [[คำ|this word]].
Use this for every Thai word in the text. This is exactly what distinguishes a guide from a dead page: the reader can dive into any word without interrupting their reading.
[[colors]] — enable consonant highlighting. A tag anywhere in the text enables the coloring of consonants by class on that page, without affecting the reader's global settings. This is needed where the colors themselves are the subject of discussion.
Two Languages
Languages are switched via tabs in the editor. Russian is our source language: the audience is Russian-speaking, as are the editors. The English version is created via translation.
AI handles the translation. After saving a published page, the translation into the second language is queued automatically, in approximately 15 minutes — this delay is necessary so that a series of small edits doesn't trigger the translation ten times. You can translate immediately using the button, or cancel the scheduled translation.
The entire text is not translated from scratch, but rather the changes — the model receives the previous version and the difference, so already corrected English is not rewritten unnecessarily.
Therefore, the rule is: do not edit the English version until the Russian version has stabilized. Otherwise, your edits will be overwritten by the next translation.
AI Editing
The ✦ AI Edit button changes the current text based on a written description: "add three examples with อัน", "reformat as a table". The result is inserted into the editor but not saved — read it first, then save.
History
Every page and every language has a version history, with the ability to view and revert. A version is saved before every AI change, so both translations and AI edits can be rolled back.
Publication
Three states: draft, published, archived. Drafts are visible only to editors. The slug (page address) can be changed while the page is a draft; after publication, it is fixed to avoid breaking other people's links.
Editing Dictionary Entries
An entry has a full editor: Thai spelling, romanization, IPA, type, verification mark, original request text, hint for re-analysis, and raw analysis JSON.
Be careful with romanization: it is stored in the entry and used in search. For entries coming from thai-language.com, it may differ from what our romanizer produces — this is expected, not an error. → Romanization and Tones
↻ Re-analyze restarts the analysis and allows you to attach a hint — "the tone of the second syllable is wrong", "add an example in a formal style". The previous analysis is erased in the process, so if the entry is generally good and only one detail is wrong, it is faster to fix it manually.
AI Sections
Additional sections for dictionary entries, each with its own request to the model. Extensions → New Extension: name (which is also the section heading) and the request text. The request can be written in any language; the response will always come in both Russian and English.
- Public — the section appears for everyone and is automatically included in every new analysis.
- Private — visible to you and those to whom you have given a token.
Inactive extensions stop being generated, but already created responses are preserved.
Public extensions should be created with caution: they are added to every new analysis and cost money for every word. Try them in private first, then open them.
Rules for Writing Guides
- Name things exactly as they are labeled in the interface. "Collections," not "folders"; "AI Analysis," not "AI-analysis." A guide that invents its own names is worse than no guide at all.
- Write only about what exists. There are some placeholder commands left in the bot and a few non-working buttons for administrators on the pages. These do not need to be documented.
- State what requires login. Voice-over, AI, collections, and training are only available after login; search and reading are not.
- Verify examples. Take romanization and tones in examples from the Romanizer, not from memory. And remember that the word page shows the saved romanization, which may differ from the calculated one.