DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to write a long-form blog post and get a Notion page link with Marketing Team Eve Template

Have the content marketer draft a blog post or landing page and return a Notion page to edit.

Who it is forA content marketer or solo founder who needs a blog post, case study, or landing page drafted against the product's existing messaging.

The problemLong-form drafts take hours to start from a blank page, and they drift from the product's positioning if the writer does not have that context.

The outcomeA Notion page with a draft that follows the team's brand context, returned as a link you can edit.

What you need first

  • A Vercel account to run the one-click deploy
  • A Typefully API key for the social drafts
  • A Notion, Resend, and Slack connection provisioned through the deploy
  • A verified sending domain and at least one segment in Resend before the first email campaign
  • Node 24.x and pnpm if you want to run it locally

Steps

  1. Deploy the template with the one-click deploy button and connect Notion when prompted.
  2. Open the team in Slack or run pnpm dev in the terminal.
  3. Ask the lead for the piece, including the topic, the audience, and the length you want.
  4. Open the Notion page link the content marketer returns and edit the draft.
  5. If you want the team's product claims updated, ask the product marketer to revise the brand context document.

Prompt for your agent

Using vercel-labs/marketing-team-eve-template, ask the lead agent to have the content marketer write a blog post about <topic> for <audience>. Expected output: a Notion page link to the draft. Verify that the draft uses the product claims in the brand context document.

Caveat. Drafts land in Notion through the Notion connector, so the quality of the output depends on how complete the brand context document is.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page