Get paid to write articles, record tutorials, and produce videos about generative UI and the OpenUI ecosystem.

We're building the definitive content library for generative UI, and we want developers like you to help create it. Write a tutorial, record a screencast, film a TikTok/YT video. If it helps developers build better AI interfaces, we want to see it.

This program runs entirely on GitHub:

1. Browse open issues: each issue is a content brief with a topic, requirements, and bounty label
2. Claim a topic: comment on the issue with a short outline or pitch
3. Get assigned: we assign one creator per topic at a time
4. Create: write your article or produce your video following our guides
5. Submit a PR: written content as markdown, video submissions as a metadata file linking to an unlisted upload
6. Review: we provide feedback via PR comments (up to 2 rounds)
7. Publish & get paid: merged PR = published content = payment triggered

We are not currently accepting new unsolicited content issues or topic requests.

Only GitHub issues labeled with the official tag will be reviewed and moderated by the OpenUI team. Any non-official issues, pitches, or self-created bounty requests may be closed without review.

If you'd like to propose a new topic, please wait for an official call for submissions or a moderator-approved discussion thread.

Pay is negotiable based on experience, production quality, and complexity. Bounty amounts are displayed as labels on each GitHub issue so you know the exact rate before you start.

Content areas include:

• Generative UI concepts: what it is, why it matters, design patterns, architecture decisions
• OpenUI framework: react-lang, react-headless, react-ui
• Integrations: OpenUI + LangChain, OpenUI + Vercel AI SDK, OpenUI + AG-UI, etc.
• Use cases: customer support bots, data dashboards, internal tools, copilots
• Comparisons: generative UI vs. traditional chat, OpenUI vs. building from scratch
• AI agent UX: best practices for agent-driven interfaces

Have a topic idea that's not listed? Open an issue and pitch it.

• All code samples work against current OpenUI API versions
• Tutorials include a companion GitHub repo with running code
• Proper attribution for third-party images or references

The best pieces in this program will be useful to developers even if they never use OpenUI. Write about generative UI as a discipline, the patterns, the tradeoffs, the real problems. OpenUI and C1 should appear where they're the natural tool for the job, not as the predetermined answer to every question. Tutorials and integration guides will obviously center on OpenUI APIs. Articles and explainers shouldn't read like product pitches.

Your writing should sound like a developer explaining something to another developer, not like a language model filling space. Examples of what gets rejected:

• "In today's rapidly evolving landscape..."
• "Generative UI is revolutionizing the way developers build interfaces"
• "Let's dive deep into..."
• "This powerful tool enables seamless integration"

If it could appear in any AI tutorial with the nouns swapped out, rewrite it.

• Developer-to-developer: conversational but precise
• Code-first: show, don't just tell
• Evergreen where possible: avoid pinning to specific versions unless necessary
• OpenUI / Thesys products should appear naturally, not be force-fitted

• Screen recordings: 1080p minimum, 4K preferred for YouTube
• Clear audio
• Code on screen must work and match any companion repo
• No watermarks from screen recording tools
• Captions/subtitles included (auto-generated is fine if accuracy-checked)

• Vertical 9:16 aspect ratio
• 30–90 seconds (60 sec sweet spot)
• Hook in the first 2 seconds: lead with the result, not the setup
• Text overlays for key points (many viewers watch without sound)
• End with a clear CTA or result shot

• Horizontal 16:9 aspect ratio
• 5–15 minutes (tighter is better)
• Timestamps/chapters in the description
• Companion GitHub repo linked in the description
• Thumbnail provided (1280×720, high contrast, readable text)

• Authentic developer energy: not overly polished corporate, not sloppy
• Show real code, real terminal output, real results
• Pacing: fast enough to hold attention, slow enough to follow along
• Branding should feel natural, not a sponsorship read

AI tools are fine for drafting scripts or articles. The bar: the final output must be indistinguishable from expert-created content. You're responsible for accuracy, originality, and quality regardless of tools used. Generic or lazy AI output (written or AI-generated voiceover) will be rejected.

You'll receive payment after your PR is merged.

Bounty amounts are displayed as labels on each GitHub issue so you know the rate before you start.

When APIs or SDKs change, the Thesys team updates the canonical version on the OpenUI blog and DEV.to. If the article is cross-posted on your own blog or channel, we'll notify you with the specific changes needed and ask you to update your version with a note like: "Updated [date] to reflect changes in [API/SDK version]." We won't silently let tutorials rot — if something breaks, we fix it or pull it.

You retain copyright. By submitting, you grant Thesys Inc a perpetual, non-exclusive license to publish, repost, clip, and embed your content. You can cross-post to your own channels immediately after publication.

For video content specifically:

• OpenUI may clip long-form videos into short-form content with creator credit
• OpenUI may upload to its own channels with creator attribution
• Creators can opt out of re-editing at submission time

Videos are published on the creator's own channel by default. OpenUI may repost or clip to its own accounts with credit. Creators without an established channel can publish directly to OpenUI accounts.