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: Design Conference Page.
Required content and structure
Build an event narrative with tracks, schedule, speaker roles, venue and ticket options.
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: paper white, deep navy and quiet pale-blue panels; precise grid and spacious typography. 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 confirmed speaker list, tracks, session times, venue details and ticket conditions. Include timezones and identify sessions that still lack a confirmed speaker or room.
Layout and behavior
Use the event theme to frame the page, then prioritize schedule navigation and attendance logistics. Keep speaker biographies secondary to session subjects and times.
Task-specific acceptance check
- Show timezone and ticket conditions without inventing speakers.
- Test overlapping sessions, a long talk title and a sold-out ticket type.
- The schedule should remain readable on mobile without hiding the timezone or access requirements.
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 Design Conference 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: Build an event narrative with tracks, schedule, speaker roles, venue and ticket options. Use the following task-specific layout guidance when translating the image into editable elements: Use the event theme to frame the page, then prioritize schedule navigation and attendance logistics. Keep speaker biographies secondary to session subjects and times.
Visual direction from the example brief
paper white, deep navy and quiet pale-blue panels; precise grid and spacious typography.
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: Build an event narrative with tracks, schedule, speaker roles, venue and ticket options. Show timezone and ticket conditions without inventing speakers. 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 Design Conference Page Design Prompt
Use this design conference page design prompt to build an event narrative with tracks, schedule, speaker roles, venue and ticket options.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Connect Tracks, Sessions and Ticket Choices
A conference page must support planning as well as promotion.
Speakers, tracks, times and ticket conditions should connect rather than appear as unrelated attractive sections. Use the event theme to frame the page, then prioritize schedule navigation and attendance logistics. Keep speaker biographies secondary to session subjects and times.
From the Prompt
Use the event theme to frame the page, then prioritize schedule navigation and attendance logistics.
Make It Your Own
Build [SCHEDULE] with explicit timezone and track labels. Associate each session with its supplied speakers, then explain which sessions and benefits each [TICKET_TYPE] includes.
Prepare the Design Conference Page Content
The track cards introduce distinct subject areas beneath the event hero. Supply the actual track names and topics before connecting them to sessions.
Prepare the confirmed speaker list, tracks, session times, venue details and ticket conditions. Include timezones and identify sessions that still lack a confirmed speaker or room.
From the Prompt
Build an event narrative with tracks, schedule, speaker roles, venue and ticket options.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this design conference page. Prepare the confirmed speaker list, tracks, session times, venue details and ticket conditions. Include timezones and identify sessions that still lack a confirmed speaker or room. Identify missing inputs before replacing them with demonstration content.
Test a Schedule Conflict
The lower area combines a timed schedule, venue information and ticket tiers. Test timezone clarity, sold-out states and ticket destinations using real event details.
Compare two sessions at the same time. Keep track, venue and access conditions visible so attendees can make a realistic choice. Test overlapping sessions, a long talk title and a sold-out ticket type. The schedule should remain readable on mobile without hiding the timezone or access requirements.
From the Prompt
Show timezone and ticket conditions without inventing speakers.
Make It Your Own
Review the design conference page against this requirement: Show timezone and ticket conditions without inventing speakers. Test overlapping sessions, a long talk title and a sold-out ticket type. The schedule should remain readable on mobile without hiding the timezone or access requirements. Preserve approved content and revise only the parts that fail this check.
Review Your Design Conference 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 overlapping sessions, a long talk title and a sold-out ticket type. The schedule should remain readable on mobile without hiding the timezone or access requirements.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current design conference page. Test overlapping sessions, a long talk title and a sold-out ticket type. The schedule should remain readable on mobile without hiding the timezone or access requirements. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
