By role

For marketers

A marketer's path through EasyCode: sessions for content, decks and films in the studio, sharing for review, and announcing a release.

Last updated November 15, 2026View as Markdown

What does EasyCode do for a marketer?

You work beside the people who build the product, with the same agents. A session on your own harness can draft a post, a page or release notes from the real tasks and pull requests. In the Studio, a session makes a deck or a film about a feature, and your team reviews it with comments before anyone outside sees it.

Your path

Follow these pages in order. Each line says why it matters to you.

Get set up

  1. Quickstart: join your org and find Sessions and Studio in the rail.
  2. Desktop app: studio sessions start there, and films and PDF exports render there.
  3. Harnesses on your own login: any of the seven harnesses works. Pick the one you already use.

Write and make

  1. Start a session: ask the agent to draft from a product's tasks and repos, so the copy matches what was built.
  2. Share and review in the studio: make a deck or a film, publish versions, collect comments, and share a link.
  3. Bring your kit: your writing guides and skills become the org's, so every session writes in your voice.

Ship and announce

  1. Ship and announce a feature: from the merged work to the people who need to hear about it.
  2. Workflows, gates and the board: see where a feature stands before you announce it.

What can I make in the studio?

A deck

Deck makes slides at 1920 × 1080. Present shows them full screen. Export PDF prints every slide, one per page, on your desktop app.

A film

Film starts from a beat sheet or a pull request, with voice, music and sound effects. The desktop app renders a 1080p MP4 at 30 frames a second: a 16:9 master or a 1:1 square.

A drawing

Drawing makes an illustration or a diagram for a post or a slide.

In the session, the agent finds music and effects in the sound kit with studio_sounds, records a voice take with studio_voice_take, and publishes a version with studio_publish.

How do I get it reviewed?

Share the piece with people in your org and give each a role, so they can comment. For people outside the org, Make a view-only link: anyone with it can read that version, with no account, no comment box and no download. You can turn the link off at any time.

Gated

The Studio is a module, so your org may not have it. Voice needs the org's integrations module beside the studio. EasyCode staff can pause the studio for an org with the studio switch.

Where next

Something wrong or missing? Suggest a change

On this page