A ConvertKit issue is the email layout, not a writer vlog

The object is the designed broadcast: hierarchy, buttons, header type. Newsletter writers is the person. ConvertKit's SKU is the issue still. Seedream holds the layout.

A ConvertKit issue that sells the product is a picture of the send: masthead, subject-adjacent headline, the button a reader will actually click, type that survives a pause. It is not a talking writer at a desk promising "this week's issue." The person is a different audience page. The SKU is the layout.

The issue still is the SKU

ConvertKit sells a designed broadcast: columns, a header lockup, a CTA button, the hierarchy a reader sees before they scroll. That screen is already a still. Motion is optional. A constructed person pointing at a fake Subscribe button is a different object, and it is not the issue.

Capture the real issue you would ship: title matching the send, button copy matching the template, type matching the brand kit. Crop chrome that is not the SKU. Crop other people's emails if a test send leaked one. The still is a document. Treat it like one.

Do not prompt a video model to "show a premium newsletter with a glowing CTA." It will invent a cousin ESP, a cousin headline, a cousin button. A reader who lands on the real ConvertKit issue and sees a different hierarchy is not looking at creative. They are looking at a lie.

If you do not have a screenshot yet, you still do not invent a host. You typeset a mock of the issue.

Newsletter-writers is the person

Newsletter writers convert with one sharp insight from the latest issue, delivered to camera, not with a bare subscribe link. Three posts a week. 9:16. X and Threads. The film ideas on that page are a talking-to-camera insight, a screen-recording scroll through a recent issue, a desk setup. That is the writer. It is not ConvertKit's product plate.

Do not twin that /for as a second ConvertKit homepage. A vlog of "why you should subscribe" is occupancy of a person. A layout still is occupancy of a send. Mixing them is how an ESP ships a generated writer, and how a writer ships a fake issue as proof they sent.

Email marketing teams are nearby on the other side. Their job is a still frame compelling enough to earn the click, with the full video waiting on the landing page, because most inboxes will not autoplay. That page is campaign mechanics. This page is the issue as a designed SKU. Do not rewrite either /for. Own the layout.

The ConvertKit plate stays empty of invented hosts. The button is the CTA. The hierarchy is the product.

Seedream 5 Pro holds the layout

Seedream 5.0 Pro is ByteDance's flagship text-to-image model: deep-thinking prompt understanding, native text rendering in 14 languages, and precise control over dense layouts and structured designs. Content type is image. Category is text-to-image only. Quality chip: 2K. Display price: 7 credits. Audio is null.

That is why the layout lives here. A ConvertKit issue is a dense layout: header, deck, button, a second beat. Video models scramble type while they also invent a desk. Seedream is the review. 7 credits, no soundtrack, no clip length. Lock it. Then decide if you even need motion.

Generate an image from text is the named agent job: a prompt in, a still out, the image row you pick. Cost is priced per model, shown before you confirm. This is not a talking clip. This is not a vlog. Dispatch Seedream 5 Pro when the brief is hierarchy. Quote every string a reader will proof: the issue title, the button, the one-line deck. "A stylish newsletter" is how you get a plausible button you cannot ship.

Pick the frame the feed will inherit. A 9:16 crop of a desktop issue is a crop you make on purpose, not a prompt that says "mobile." Proof at 100%. One wrong character in the header is a regenerate. Seedream is not ConvertKit. It typesets a picture of a layout. Do not bake a made-up open-rate into the generate.

Ideogram is the lockup, not a vlog

Ideogram V4 is the lettering row: 6 credits, text-to-image, text rendering, posters and logos listed. Use it when the brief is a masthead word, a wordmark, a single CTA string on a plate. Ideogram is not a writer.

The split is practical. Seedream holds dense hierarchy — several blocks, a button, a deck. Ideogram holds a lockup — the name, the one line. Neither row talks. Neither row is a desk vlog. The text-to-image studio is the door for both. Pick the row, quote the strings, proof the glyphs.

Do not:

• Text-to-video a luxury studio with a glowing ConvertKit-colored button.
• Generate a twin of the writer pointing at a subject line the model invented.
• Bake earnings or open-rate theatre into the plate.

Change the headline with a new still. Change the button with overlay if you later animate. Keep the host off this plate. Pause on the header. Is it the issue you send? Yes: ship. No: you asked a video model for a vlog. Go back to the layout.

FAQ

Can I generate a prettier issue instead of capturing the ConvertKit send?

You can typeset a mock on Seedream 5 Pro if you quote the real strings and proof them. You cannot invent an ESP, a button, or a headline. The live issue still is the honest SKU. Overlay the production string if the mock is only a crop.

Is the newsletter-writers /for page the ConvertKit brief?

No. Newsletter writers is the person: one insight to camera, a scroll through a recent issue, a desk. ConvertKit's SKU is the designed broadcast. Copying their talking-to-camera instinct is how you get a writer vlog instead of a layout.

Why Seedream 5 Pro instead of Ideogram V4?

Dense hierarchy versus a lockup. Seedream is 7 credits, 14 languages, structured layouts, 2K quality chip. Ideogram V4 is 6 credits, posters and logos, accurate text rendering. An issue with header, deck, and button is Seedream. A masthead word is Ideogram. Neither is a vlog.

Does generate-an-image-from-text make a talking writer?

No. It is the named stills job: prompt in, image out, model you pick. Dispatch Seedream or Ideogram. A talking clip is a different capability on a different day, with a real named person if someone must speak.