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 Homepage.
Required content and structure
Introduce the community purpose, upcoming activities, contribution paths and conduct resources.
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
Collect the community purpose, current activities, contribution options, conduct guidelines and real joining destinations. Mark activities as upcoming, ongoing or completed.
Layout and behavior
Help a newcomer choose one first action: attend, contribute or join a conversation. Use activities to show what participation looks like instead of relying on unverified membership counters.
Task-specific acceptance check
- Do not invent member counts or imply every event is currently open.
- Check a visitor with no prior community context.
- Closed events need an appropriate archive or recap link, and contribution routes should explain what is expected before asking for commitment.
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 Homepage. 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: Introduce the community purpose, upcoming activities, contribution paths and conduct resources. Use the following task-specific layout guidance when translating the image into editable elements: Help a newcomer choose one first action: attend, contribute or join a conversation. Use activities to show what participation looks like instead of relying on unverified membership counters.
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: Introduce the community purpose, upcoming activities, contribution paths and conduct resources. Do not invent member counts or imply every event is currently open. 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 Homepage Design Prompt
Use this community homepage design prompt to introduce the community purpose, upcoming activities, contribution paths and conduct resources.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Give New Members a Clear First Contribution
A community homepage needs a path from understanding its purpose to participating.
A wall of activities without eligibility or status can leave newcomers unsure where they belong. Help a newcomer choose one first action: attend, contribute or join a conversation. Use activities to show what participation looks like instead of relying on unverified membership counters.
From the Prompt
Help a newcomer choose one first action: attend, contribute or join a conversation.
Make It Your Own
Introduce [COMMUNITY_PURPOSE], then separate attending an activity, contributing work and finding conduct resources. Show [EVENT_STATUS] and the requirements for each contribution path.
Prepare the Community Homepage Content
The activities panel shows dated sessions with concise titles. Provide maintained event records and clear destinations so the homepage does not become a stale schedule.
Collect the community purpose, current activities, contribution options, conduct guidelines and real joining destinations. Mark activities as upcoming, ongoing or completed.
From the Prompt
Introduce the community purpose, upcoming activities, contribution paths and conduct resources.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this community homepage. Collect the community purpose, current activities, contribution options, conduct guidelines and real joining destinations. Mark activities as upcoming, ongoing or completed. Identify missing inputs before replacing them with demonstration content.
Test a First-Time Visitor’s Route
Adjacent panels distinguish ways to participate from reference resources. Verify that each route lands on the relevant contribution or guidance page.
Choose one activity and one contribution option. Both should explain the next step without requiring knowledge of internal channels or an invented membership scale. Check a visitor with no prior community context. Closed events need an appropriate archive or recap link, and contribution routes should explain what is expected before asking for commitment.
From the Prompt
Do not invent member counts or imply every event is currently open.
Make It Your Own
Review the community homepage against this requirement: Do not invent member counts or imply every event is currently open. Check a visitor with no prior community context. Closed events need an appropriate archive or recap link, and contribution routes should explain what is expected before asking for commitment. Preserve approved content and revise only the parts that fail this check.
Review Your Community Homepage Result
Generated copy, routes and visual structure require review. Do not connect real forms, payments or external services without implementing and testing those flows.
- Check a visitor with no prior community context. Closed events need an appropriate archive or recap link, and contribution routes should explain what is expected before asking for commitment.
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 homepage. Check a visitor with no prior community context. Closed events need an appropriate archive or recap link, and contribution routes should explain what is expected before asking for commitment. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
