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…
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 tag, links, image assets). Returns a scorecard, findings by severity, and prioritized edits. Use when a draft exists…
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 + tag, scannable formatting, and copy-pasteable commands. Use after an outline exists (from blog-plan) and it's time to draft. Trigger…
Modify the openvidu.io website (this repo) — landing, pricing, docs for OpenVidu Meet and OpenVidu Platform, blog-adjacent pages, templates, navigation, styling. Routes each task to the canonical doc in contributing/. Trigger phrases like "edit the website", "change the landing page", "update the pricing page", "add a…
Publish an OpenVidu documentation version end to end — update the releases pages with their strict heading and link contract, write the version-pinned Release blog post, choose and dispatch the right Publish Web command (new/latest/past), and interpret the post-publish verification. Use for any release-day docs work…
Record a looping demo video of an app that embeds OpenVidu Meet, with two synthetic camera feeds (e.g. a "user" and a "client") so the meeting looks real without any physical webcams. Covers injecting stock/video-file cameras into OpenVidu Meet via getUserMedia override, driving the join through the real browser, and…
★not rated 5 6d agoA125 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: