Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create a responsive HTML website using the existing project stack for [PROJECT] and [AUDIENCE]. The task is: Newsletter Signup Page.
Required content and structure
Explain the editorial promise, show an issue sample, frequency and subscribe form.
Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.
Design direction
Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: warm cream, muted olive and terracotta; tactile materials and a calm editorial rhythm. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Prepare the newsletter's subject, intended reader, actual or planned cadence, an issue sample and subscription consent wording. Define what confirmation means for this signup.
Layout and behavior
Show the editorial value through the sample and a few concrete topics. Keep the form short and explain confirmation, preferences and unsubscribe expectations in plain language.
Task-specific acceptance check
- Keep subscription consent and confirmation states explicit.
- Test invalid input, an existing subscriber and a failed request.
- The success message must match the implemented state, such as confirmation email sent rather than subscription completed.
Implementation and review
Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for Newsletter Signup Page. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Explain the editorial promise, show an issue sample, frequency and subscribe form. Use the following task-specific layout guidance when translating the image into editable elements: Show the editorial value through the sample and a few concrete topics. Keep the form short and explain confirmation, preferences and unsubscribe expectations in plain language.
Visual direction from the example brief
warm cream, muted olive and terracotta; tactile materials and a calm editorial rhythm.
Interaction specification
The reference is a static concept: the behavior below is a requirement to implement, not proof that the picture already works. Copy the customized prompt into your working project. Start with the core task: Explain the editorial promise, show an issue sample, frequency and subscribe form. Keep subscription consent and confirmation states explicit. For each visible control, specify its trigger, affected state and feedback; implement local changes with consistent state across related views. Give search and filters real results, selection controls an explicit active state, and save actions visible pending/success/failure feedback where relevant. Do not add unrelated workflows. Use proper links for navigation, buttons for actions and accessible names for icon controls. Do not imply a backend operation succeeded when only a local demo changed.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a Newsletter Signup Page Design Prompt
Use this newsletter signup page design prompt to explain the editorial promise, show an issue sample, frequency and subscribe form.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Make the Editorial Promise Concrete
A newsletter signup should tell readers what they will receive and how often.
A vague invitation to stay updated provides little basis for giving an email address. Show the editorial value through the sample and a few concrete topics. Keep the form short and explain confirmation, preferences and unsubscribe expectations in plain language.
From the Prompt
Show the editorial value through the sample and a few concrete topics.
Make It Your Own
Describe [EDITORIAL_FOCUS], show [SAMPLE_ISSUE] and state [FREQUENCY]. Keep the form concise and explain the subscription and confirmation steps in plain language.
Prepare the Newsletter Signup Page Content
The email field and consent copy sit directly under the editorial pitch; specify validation, consent handling and a truthful submission result.
Prepare the newsletter's subject, intended reader, actual or planned cadence, an issue sample and subscription consent wording. Define what confirmation means for this signup.
From the Prompt
Explain the editorial promise, show an issue sample, frequency and subscribe form.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this newsletter signup page. Prepare the newsletter's subject, intended reader, actual or planned cadence, an issue sample and subscription consent wording. Define what confirmation means for this signup. Identify missing inputs before replacing them with demonstration content.
Check the Signup Outcome
The sample issue makes the offer tangible through a lead story and short article list; use approved sample content rather than promising unseen material.
Show validation and confirmation without losing the address after a recoverable error. Do not claim a subscription succeeded when only a local form state changed. Test invalid input, an existing subscriber and a failed request. The success message must match the implemented state, such as confirmation email sent rather than subscription completed.
From the Prompt
Keep subscription consent and confirmation states explicit.
Make It Your Own
Review the newsletter signup page against this requirement: Keep subscription consent and confirmation states explicit. Test invalid input, an existing subscriber and a failed request. The success message must match the implemented state, such as confirmation email sent rather than subscription completed. Preserve approved content and revise only the parts that fail this check.
Review Your Newsletter Signup Page Result
Generated copy, routes and visual structure require review. Do not connect real forms, payments or external services without implementing and testing those flows.
- Test invalid input, an existing subscriber and a failed request. The success message must match the implemented state, such as confirmation email sent rather than subscription completed.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current newsletter signup page. Test invalid input, an existing subscriber and a failed request. The success message must match the implemented state, such as confirmation email sent rather than subscription completed. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
