Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Add a new expert to the Remotion experts page
Review the instructions the agent will receive before you install.
Add the expert's photo to both:
packages/docs/static/img/freelancers/<firstname>.pngpackages/promo-pages/public/img/freelancers/<firstname>.pngThe image should be a square headshot (PNG format). Both paths must have the same file.
Add an entry to the experts array in packages/promo-pages/src/components/experts/experts-data.tsx:
{
slug: 'firstname-lastname',
name: 'First Last',
image: '/img/freelancers/<firstname>.png',
website: 'https://example.com' | null,
x: 'twitter_handle' | null,
github: 'github_username' | null,
linkedin: 'in/linkedin-slug/' | null,
email: 'email@example.com' | null,
videocall: 'https://cal.com/...' | null,
since: new Date('YYYY-MM-DD').getTime(),
description: (
<div>
A short description of the expert's work and specialties.
Links to projects can be included with <a> tags.
</div>
),
},
since should be set to today's dateslug must be lowercase, hyphenated version of the namenullexperts array (before the closing ])Render the expert card by running in packages/docs:
bun render-cards
This generates packages/docs/static/generated/experts-<slug>.png. Verify it says "Rendered experts-<slug>" (not "Existed").
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.
Add browser WebCodecs bugs to the Remotion Mediabunny documentation. It checks the linked issue’s title, filing date, reporter, and resolution, then adds a table row while preserving the existing format.