Add Documentation Page
You are adding a new documentation page to the GramIO docs site.
Arguments
The user provides [section/page-name] — e.g., guides/webhooks or plugins/official/my-plugin.
Steps
Read AGENTS.md for conventions (frontmatter, bilingual sync, image rules).
Create the English page at
docs/{section}/{page-name}.md:- Add YAML frontmatter with
title,descriptionmeta, andkeywordsmeta. - Add an H1 heading matching the title.
- Add a brief introductory paragraph placeholder.
- Follow existing page patterns in the same section (read a sibling page for reference).
- Add YAML frontmatter with
Create the Russian translation at
docs/ru/{section}/{page-name}.md:- Translate the frontmatter (
title,description,keywords) to Russian. - Translate the H1 heading and all body content to Russian.
- Preserve code blocks, twoslash annotations, and markdown structure exactly.
- Use the
/translate-pageskill conventions for translation quality.
- Translate the frontmatter (
Register in EN sidebar — edit
docs/.vitepress/config/locales/en.locale.ts:- Find the appropriate section in the sidebar config.
- Add the new page link following existing patterns.
Register in RU sidebar — edit
docs/.vitepress/config/locales/ru.locale.ts:- Find the matching section.
- Add the new page link with
/ru/prefix.
Update
public/_redirectsif the page was moved or renamed from a previous location:- Add a
301!redirect from the old path to the new path. - Add a corresponding
/ru/redirect if the RU page also moved. - Note:
_redirectsis Netlify-specific; GitHub Pages does not support it.
- Add a
Report what was created and where the user should add content.