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: Team About Page.
Required content and structure
Explain the organization's purpose, people, disciplines and working approach.
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 approved biographies, portraits, disciplines and role titles, plus a short account of how the team works. Obtain the actual organization story rather than filling it with generic values.
Layout and behavior
Connect purpose to people and working practices. Use consistent biography length and portrait treatment, allowing contributors' roles to remain clear in both grid and mobile list views.
Task-specific acceptance check
- Use approved biographies and portraits with accurate roles.
- Check long names, people without portraits and collaborative roles.
- Avoid visual hierarchy that accidentally suggests seniority or ownership that the content does not establish.
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 Team About 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 organization's purpose, people, disciplines and working approach. Use the following task-specific layout guidance when translating the image into editable elements: Connect purpose to people and working practices. Use consistent biography length and portrait treatment, allowing contributors' roles to remain clear in both grid and mobile list views.
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: Explain the organization's purpose, people, disciplines and working approach. Use approved biographies and portraits with accurate roles. 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 Team About Page Design Prompt
Use this team about page design prompt to explain the organization's purpose, people, disciplines and working approach.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Connect People to the Organization’s Work
An about page should explain what the organization does and how its people contribute.
A portrait grid alone leaves the relationship between disciplines and working approach unclear. Connect purpose to people and working practices. Use consistent biography length and portrait treatment, allowing contributors' roles to remain clear in both grid and mobile list views.
From the Prompt
Connect purpose to people and working practices.
Make It Your Own
Introduce [PURPOSE], group [TEAM_PROFILES] by the roles relevant to the work and explain the working approach with concrete practices. Use approved biographies and portraits.
Prepare the Team About Page Content
Portrait cards repeat name and role; supply approved biographies and avoid using fictional example people as real staff.
Collect approved biographies, portraits, disciplines and role titles, plus a short account of how the team works. Obtain the actual organization story rather than filling it with generic values.
From the Prompt
Explain the organization's purpose, people, disciplines and working approach.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this team about page. Collect approved biographies, portraits, disciplines and role titles, plus a short account of how the team works. Obtain the actual organization story rather than filling it with generic values. Identify missing inputs before replacing them with demonstration content.
Check a Profile Without Its Photograph
The working process follows the people section; describe actual collaboration steps instead of a generic culture claim.
The person's name, role and contribution should remain understandable. Avoid implying credentials or responsibilities that are not in the supplied biography. Check long names, people without portraits and collaborative roles. Avoid visual hierarchy that accidentally suggests seniority or ownership that the content does not establish.
From the Prompt
Use approved biographies and portraits with accurate roles.
Make It Your Own
Review the team about page against this requirement: Use approved biographies and portraits with accurate roles. Check long names, people without portraits and collaborative roles. Avoid visual hierarchy that accidentally suggests seniority or ownership that the content does not establish. Preserve approved content and revise only the parts that fail this check.
Review Your Team About 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.
- Check long names, people without portraits and collaborative roles. Avoid visual hierarchy that accidentally suggests seniority or ownership that the content does not establish.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current team about page. Check long names, people without portraits and collaborative roles. Avoid visual hierarchy that accidentally suggests seniority or ownership that the content does not establish. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
