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: Community Event Detail.
Required content and structure
Provide the session goal, host, date, timezone, format, agenda and participation requirements.
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: strong black typography, warm yellow panels and sharp geometric compositions; controlled contrast. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Gather the confirmed host, session purpose, date, timezone, format, location and participation requirements. Clarify whether registration is open and what cancellation or access conditions apply.
Layout and behavior
Let someone answer what they will do, when to arrive and how to join before reading the full agenda. Group practical details together rather than scattering them across decorative cards.
Task-specific acceptance check
- Make registration status and cancellation details easy to find.
- Test a remote event, a full event and a changed start time.
- Keep registration status and joining instructions consistent across the primary action and event details.
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 Community Event Detail. 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: Provide the session goal, host, date, timezone, format, agenda and participation requirements. Use the following task-specific layout guidance when translating the image into editable elements: Let someone answer what they will do, when to arrive and how to join before reading the full agenda. Group practical details together rather than scattering them across decorative cards.
Visual direction from the example brief
strong black typography, warm yellow panels and sharp geometric compositions; controlled contrast.
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: Provide the session goal, host, date, timezone, format, agenda and participation requirements. Make registration status and cancellation details easy to find. 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 Community Event Detail Design Prompt
Use this community event detail design prompt to provide the session goal, host, date, timezone, format, agenda and participation requirements.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Make Participation Requirements Part of the Invitation
An event detail page must let visitors decide whether they can participate.
The date, timezone, format and prerequisites matter as much as the promotional session description. Let someone answer what they will do, when to arrive and how to join before reading the full agenda. Group practical details together rather than scattering them across decorative cards.
From the Prompt
Let someone answer what they will do, when to arrive and how to join before reading the full agenda.
Make It Your Own
Group [SESSION_GOAL], [HOST], [DATE_TIME_TIMEZONE] and [FORMAT] near registration. Show the agenda, preparation requirements and cancellation information before the final action.
Prepare the Community Event Detail Content
The lower content separates a timed agenda from equipment and participation requirements. Supply actual timings and access needs before asking visitors to register.
Gather the confirmed host, session purpose, date, timezone, format, location and participation requirements. Clarify whether registration is open and what cancellation or access conditions apply.
From the Prompt
Provide the session goal, host, date, timezone, format, agenda and participation requirements.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this community event detail. Gather the confirmed host, session purpose, date, timezone, format, location and participation requirements. Clarify whether registration is open and what cancellation or access conditions apply. Identify missing inputs before replacing them with demonstration content.
Check Registration States
The side panel groups registration, calendar addition and cancellation information. Test capacity, duplicate registration and cancellation feedback instead of treating all three controls as links to one form.
Represent open, full and canceled states distinctly. A registration button should not remain actionable when the event record says participation is unavailable. Test a remote event, a full event and a changed start time. Keep registration status and joining instructions consistent across the primary action and event details.
From the Prompt
Make registration status and cancellation details easy to find.
Make It Your Own
Review the community event detail against this requirement: Make registration status and cancellation details easy to find. Test a remote event, a full event and a changed start time. Keep registration status and joining instructions consistent across the primary action and event details. Preserve approved content and revise only the parts that fail this check.
Review Your Community Event Detail 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 a remote event, a full event and a changed start time. Keep registration status and joining instructions consistent across the primary action and event details.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current community event detail. Test a remote event, a full event and a changed start time. Keep registration status and joining instructions consistent across the primary action and event details. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
