I Built a Newsletter Page With Gemini. Here’s What Needed Fixing.
The first draft was editable and usable, but a missing name and undersized text still needed one precise repair.Three Lines Fixed in Small SignalsI already had the copy. What I didn’t have was a browser-ready newsletter page I could keep editing after the AI finished.Gemini Canvas gave me a…
The first draft was editable and usable, but a missing name and undersized text still needed one precise repair.Three Lines Fixed in Small SignalsI already had the copy. What I didn’t have was a browser-ready newsletter page I could keep editing after the AI finished.Gemini Canvas gave me a single-file HTML draft on the first pass. It stayed readable on desktop and phone, but the visible page had no publication name. Two reader-facing lines were also smaller than the legibility floor I had set.One focused revision fixed those issues without rewriting the approved copy or changing the page structure. The result was a draft I could inspect, revise, download, and continue editing.Google’s Canvas help page, which I checked on September 8, describes Canvas as a place to create and edit code and web pages.It doesn’t promise a finished newsletter or responsive quality. I treated its output as a draft.I gave Canvas a finished brief, not a blank pageThe copy decisions were mine. I used a fictional publication called Small Signals with a headline, three short stories, a checklist, one CTA, and a footer.I chose the constraints that mattered. The copy had to remain unchanged. The CTA had to point to the checklist. The page needed to work at a desktop width and a narrow phone width, without outside scripts, fonts, or images.This was the exact prompt I submitted:Use Canvas to build a web newsletter from the frozen brief below. Return one complete single-file HTML document with all CSS inline or inside a single element.Preserve every reader-facing string exactly as written:Publication name: Small SignalsIssue label: Issue 12 · September 2026Headline: Three checks before you publish AI-assisted workIntro: A polished draft can still hide a missing source, a changed number, or an unclear next step.Story 1 heading: Save the sourceStory 1 body: Keep the page, date, and exact passage beside every factual claim.Story 2 heading: Freeze the numbersStory 2 body: Write the expected value down before asking a tool to summarize or transform it.Story 3 heading: Name the human decisionStory 3 body: State what a person must verify before the draft can move forward.Checklist heading: The 30-second pre-publish checkChecklist items: Source saved; Numbers matched; Human decision namedCTA label: Open the checklistCTA target: #checklistFooter: No tracking pixels. No personal data.Production requirements:- Use semantic headings, three story sections, one checklist section with id="checklist", one CTA link with href="#checklist", and the exact footer.- Use no external images, fonts, scripts, trackers, or assets.- At 1440 × 900 CSS pixels, keep the readable content column no wider than 680 CSS pixels.- At 390 × 844 CSS pixels, allow no horizontal scrolling and stack all three story sections vertically.- Keep computed body copy at least 16 CSS pixels at both widths.- Make the CTA's visible target at least 44 × 44 CSS pixels.- Keep every frozen string and the CTA target unchanged. Styling may change; facts and wording may not.Create the page in Canvas and provide the full HTML document without commentary before or after the code.The opening lines of the newsletter prompt in Gemini Canvas.That prompt is longer than I would use for casual ideation because this wasn’t ideation. I wanted an editable production draft with known content and a small set of checks. Canvas still had freedom over the visual styling and HTML structure.The first version was useful, but not finishedCanvas returned a complete HTML file that I could download and inspect. The first version kept the approved story copy, produced a single-column page, stacked the sections on the phone, and kept the CTA working.But the page also made two mistakes that the layout didn’t reveal.The first was identity. Small Signals appeared in the document title but not on the visible page. A reader could see the issue date and headline without seeing the publication name.The second was text size. The issue label and footer were below the minimum I had chosen for this test. This happened in both the desktop and phone versions, so it wasn’t a mobile-only defect.The first mobile draft without the Small Signals publication name.Nothing had collapsed. There was no broken-page screenshot. The draft looked calm and plausible, which made the missing identity line easy to overlook.I asked for one repair and no redesignThe second interaction came directly from the first audit. I named the observed defects and told Canvas to preserve everything that had already worked.Revise the existing Canvas HTML. Fix only these two failed checks from the first audit:1. The publication name `Small Signals` is absent from the rendered page body. Add that exact frozen string once as visible text in the header.2. The issue label `Issue 12 · September 2026` and footer `No tracking pixels. No personal data.` both compute to 14 CSS pixels at 1440 × 900 and 390 × 844. Raise both reader-facing, non-heading text elements to at least 16 CSS pixels.Keep every other frozen string exactly unchanged, keep the CTA label `Open the checklist` and href="#checklist" unchanged, and preserve all passing layout and accessibility behavior. Do not redesign the page or add content. Return the complete revised single-file HTML document.The repair succeeded in this sample. Canvas added Small Signals once in the header and changed the two small text declarations. The saved-file comparison showed three changed lines and no other HTML or CSS changes.No redesign. No extra retry.Then I opened the revised file at the same desktop and phone widths. The publication name was visible, the two lines met my chosen minimum, and the layout, copy, CTA, and dependency checks still passed.The revised mobile draft with Small Signals above the issue label.I made only two Gemini interactions: one initial build and one targeted revision. There was no vague “make it better” comparison, so this run can’t support a claim that targeted prompts generally outperform broader ones.The account already had Google AI Pro. My incremental spend for these two interactions was USD 0.00, but this wasn’t a free-account test.How far I would use this draftI would use the revised file as an editable browser newsletter draft. It preserved the copy I supplied, worked at the two widths I checked, and remained a plain HTML file I could save and inspect.I wouldn’t treat it as a finished email template. I didn’t send it through Gmail, Outlook, Substack, Beehiiv, or an email service provider. This test says nothing about inbox rendering, deliverability, tracking, or reader response.I also wouldn’t turn my 16-pixel test floor into a universal publishing rule. It was the standard I chose for this page. Another project may need different typography, breakpoints, or accessibility requirements.For this draft, the useful handoff was simple:the approved copy stayed frozen;the first and revised HTML files were both saved;the visible identity, text, CTA, and layout checks were reviewed;the revision changed only the defects found in the first version;the final file remained editable outside Gemini.That’s enough to move this particular page forward as a draft. It isn’t enough to call Gemini a newsletter publisher, an email compatibility tool, or a substitute for the final human review.This story is published under the Generative AI publication. Connect with us on LinkedIn and follow Zeniteq to stay in the loop with the latest AI stories. Let’s shape the future of AI together!I Built a Newsletter Page With Gemini. Here’s What Needed Fixing. was originally published in Generative AI on Medium, where people are continuing the conversation by highlighting and responding to this story.Source: Generative AI Pub — Published — Category: Image AI