openvidu.io

Plan and outline an OpenVidu blog post. Use when turning a raw technical idea into a structured, SEO-optimized outline — title, article type, H1/H2/H3 structure with concrete talking points, and a buying-journey CTA — before any writing happens. Trigger phrases like "plan a blog post", "outline an article", "blog brief", "what should this post cover".

Review an OpenVidu blog draft (full post or a section) for readability, SEO, technical accuracy, CTA strength, structure, formatting, and repo-specific validity (frontmatter, categories, authors, the `<!-- more -->` tag, links, image assets). Returns a scorecard, findings by severity, and prioritized edits. Use when a draft exists and needs auditing before publish. Trigger phrases like "review this post", "is this blog ready to publish", "audit the draft", "check my article".

Write an OpenVidu technical blog post in English from a structured outline — full post or a single section — following the repo's conversational style, MkDocs frontmatter, intro hook + `<!-- more -->` tag, scannable formatting, and copy-pasteable commands. Use after an outline exists (from blog-plan) and it's time to draft. Trigger phrases like "write the post", "draft this blog", "write section X", "turn this outline into a post".

Modify the openvidu.io website (this repo, served from gh-pages at https://openvidu.io/) — landing, pricing, docs for OpenVidu Meet and OpenVidu Platform, research, support and other pages. Explains how pages are composed with MkDocs Material (nav, frontmatter, theme overrides/partials, shared snippets, tag system), the strict link rules, how the two products' docs are versioned with mike, and how to test locally with Docker. Use for any change to page content, structure, styling, templates, structured data, or navigation. Trigger phrases like "edit the website", "change the landing page", "update the pricing page", "add a docs page", "modify a section of openvidu.io".