From the creator community
GPT-6 Astra and the 35-Word Coca-Cola Landing-Page Test
A Reddit creator gave Astra and Gemini the same thirty-five-word Coca-Cola Zero landing-page brief and published the outputs. The request named a familiar brand, asked for beauty and required at least five sections with a hero at the top. It supplied no visual direction. That makes the experiment interesting to browse and limited as a production brief.
We opened the Astra page: its desktop hero uses large left-aligned copy, a dark red-and-black treatment and a prominent tilted can on the right. This article looks at the decisions the short prompt leaves to the agent, then develops an original sparkling-tea hero brief you can turn into assets in Ciyo.
Open the comparison before choosing a winner
The author, u/highsierraloft, describes one completed run per model, fresh folders and conversations, and no design edits to the published results. Astra ran through Codex CLI and Gemini through Antigravity. The creator explicitly notes that their built-in instructions and tools differ.
Treat the gallery as a comparison of these particular agent outputs. It does not isolate model quality, establish conversion performance or tell you what happens with an unfamiliar brand. The recognizable product already gives an agent strong visual associations that your new business may not have.
Original community post and creator media. Our Ciyo adaptation follows the case study.
Name the decisions hidden inside “beautiful”
For our fictional sparkling tea, the brief must choose an audience, a product reference, a visual idea and a next action. We choose an unsweetened tea concept for a quiet afternoon break, represented by an unbranded slim bottle and a pale green setting. Those are invented design inputs, not factual claims about an existing drink.
The hero should let a visitor identify the bottle, understand the page’s purpose and find one action. Specify where the headline and action will live before creating the artwork. Otherwise the image can occupy exactly the space the live copy needs.
| Decision | Original worked-example choice | Asset consequence |
|---|---|---|
| Audience and moment | A quiet afternoon break | Calm light and a restrained setting |
| Product identity | One approved unbranded slim bottle | Keep the same silhouette in every view |
| Composition | Bottle on the right, live copy on the left | Reserve a clean left third |
| Mobile layout | Copy above the bottle image | Prepare a separate square crop |
| Action | Explore the fictional product concept | Do not invent checkout, stock or reviews |
Create the hero around a copy area
In Ciyo, generate one wide hero with the approved bottle reference and the specified empty area. Keep decoration away from the headline zone. A leaf, shadow or bright reflection that looks appealing on its own can compete with the page’s most important words.
Inspect the image with temporary headline and button boxes over it in your layout tool. This checks composition before implementation. If the product is too small after leaving enough copy space, simplify the scene or use a split layout rather than shrinking the text.
Give Astra an art-direction contract
The prompt below asks for a composition and asset plan before code. It adds the information our fictional product lacks compared with a globally recognizable drink. You can still let the agent make design choices, but it should explain them in relation to the intended audience and action.
After approving the Ciyo hero, give the coding agent the actual file and the required text. Keep headings, buttons and product descriptions as live interface elements. The image should support the page rather than becoming a screenshot of the whole page.
Plan a landing-page hero for a fictional sparkling-tea concept. Audience: people looking for a quiet afternoon break. Visual direction: pale green, warm ivory, calm daylight and an approved unbranded slim bottle. Reserve the left third of the desktop hero for live headline and action text; on mobile, place copy above a separate square product crop. Return an asset brief for Ciyo, a content hierarchy and three design choices with reasons. Do not invent nutritional claims, reviews, stock or a functioning checkout. Wait for hero approval before implementing the page.Compare decisions, not just screenshots
If you test two directions, keep the product, copy and action the same. Compare a quiet studio scene with a leaf-shadow scene, for example. Changing the headline, offer and image simultaneously makes it difficult to explain why you prefer one version.
Then review the coded page at its actual desktop and mobile widths. The original Reddit gallery is useful because the outputs are inspectable pages; apply that same expectation to your own result. Check text readability, crop, keyboard focus and the destination of the primary action.
| Question | Evidence to collect | Decision |
|---|---|---|
| Is the product clear? | Both candidates at the same displayed size | Choose the clearer silhouette and crop |
| Can the copy breathe? | Actual headline over the proposed layout | Reduce visual competition |
| Does mobile preserve the hierarchy? | Narrow layout with real copy length | Create a new crop or rearrange elements |
| Does the action match the promise? | Open the actual destination | Fix the destination or revise the wording |
Keep the source experiment and your production brief separate
The Coca-Cola test is enjoyable precisely because so little direction is given. A client project has a different responsibility: communicate a particular product accurately. Save the approved hero, copy, mobile crop and the reasons for choosing the direction together.
For traffic from an Astra comparison query, show readers the actual experiment and then offer a concrete next step. That next step is making a better-specified asset for their own project, not promising that one model automatically produces a higher-converting website.
Questions about this workflow
Does the Coca-Cola comparison prove Astra beats Gemini?
It shows one completed output from each agent setup. The author notes different tools and built-in instructions, so it should not be treated as an isolated model benchmark or a conversion study.
What does Ciyo contribute to this workflow?
Ciyo creates the approved hero artwork and related crops or visual references. A separate coding workflow implements live copy, controls, responsive layout and behavior.
Create a hero with room for the message
Bring an approved product reference and decide where the live headline will sit before generating the scene.