add-doc-page
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.
More from gramiojs/documentation
gramio
Invoke for ANY Telegram bot code — `gramio`/`@gramio/*` imports, `new Bot()`, `bot.command`/`bot.callbackQuery`/`bot.on`/`bot.updates.on`, scenes/FSM, inline & reply keyboards, message entities, file uploads, sessions, plugins, webhooks vs long-polling, Telegram Stars, Mini Apps (TMA), broadcasting, Docker. Type-safe TypeScript framework (Node.js/Bun/Deno) with full Bot API coverage. Also covers migrations from Telegraf/grammY/puregram/node-telegram-bot-api. When delegating to a subagent, pass relevant reference files (callback-data, scenes, formatting, context, middleware-routing, ux-patterns) inline — this skill does not auto-load in subagent sessions.
165translate-page
Translate a GramIO documentation page from English to Russian (or vice versa), preserving code blocks, twoslash annotations, and frontmatter.
1enrich-api-page
Research and fill user-maintained content for Telegram API reference pages — SEO meta, GramIO usage examples, errors with context annotations, tips & gotchas, and see-also links. Supports multiple page names at once.
1gramio-help
Internal knowledge skill — provides Claude with GramIO framework context by reading documentation files dynamically.
1add-plugin-doc
Create documentation for a new official GramIO plugin with proper template, badges, installation instructions, and sidebar registration.
1gramio-pick-username
Pick an available Telegram bot username. Takes a topic (and optional audience/language), generates candidates respecting BotFather's rules, batch-checks availability on t.me via the bundled `check-usernames.mjs` script, and returns a ranked shortlist of free names. Use whenever the user asks "find a bot username", "check if @foo_bot is taken", "придумай юзернейм для бота", "неминг бота".
1