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: Security and Trust Page.
Required content and structure
Organize documented controls, data handling, compliance evidence and contact paths.
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
Use a supplied inventory of documented controls, data handling practices, certification evidence and contact routes. Record the scope and date of any third-party assurance material.
Layout and behavior
Organize information by the questions a buyer needs answered: access, data, operations and available evidence. Link to supporting documents without turning every control into a certification badge.
Task-specific acceptance check
- Show only verified certifications and do not infer legal guarantees.
- Trace each assurance statement to its evidence.
- If a report requires a request, say so; never imply that an unavailable report or a planned control is already verified.
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 Security and Trust 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: Organize documented controls, data handling, compliance evidence and contact paths. Use the following task-specific layout guidance when translating the image into editable elements: Organize information by the questions a buyer needs answered: access, data, operations and available evidence. Link to supporting documents without turning every control into a certification badge.
Visual direction from the example brief
Organize information by the questions a buyer needs answered: access, data, operations and available evidence. Link to supporting documents without turning every control into a certification badge.
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: Organize documented controls, data handling, compliance evidence and contact paths. Show only verified certifications and do not infer legal guarantees. 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 Security and Trust Page Design Prompt
Use this security and trust page design prompt to organize documented controls, data handling, compliance evidence and contact paths.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Attach Security Statements to Documented Scope
A trust page should explain documented controls and data handling.
Broad words such as secure do not establish what is protected, by which control or within what scope. Organize information by the questions a buyer needs answered: access, data, operations and available evidence. Link to supporting documents without turning every control into a certification badge.
From the Prompt
Organize information by the questions a buyer needs answered: access, data, operations and available evidence.
Make It Your Own
Organize [DOCUMENTED_CONTROLS], [DATA_HANDLING] and supplied evidence by topic. State scope and review dates, and provide a clear route for security inquiries.
Prepare the Security and Trust Page Content
The central cards separate security topics; provide scoped statements and documentation links instead of unverified certification claims.
Use a supplied inventory of documented controls, data handling practices, certification evidence and contact routes. Record the scope and date of any third-party assurance material.
From the Prompt
Organize documented controls, data handling, compliance evidence and contact paths.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this security and trust page. Use a supplied inventory of documented controls, data handling practices, certification evidence and contact routes. Record the scope and date of any third-party assurance material. Identify missing inputs before replacing them with demonstration content.
Read a Claim Beside Its Evidence
The evidence panel says documentation is available on request; preserve that qualification and route requests to a real contact.
Confirm that the linked document supports the exact statement. A certification covering one service should not be presented as proof about every product component. Trace each assurance statement to its evidence. If a report requires a request, say so; never imply that an unavailable report or a planned control is already verified.
From the Prompt
Show only verified certifications and do not infer legal guarantees.
Make It Your Own
Review the security and trust page against this requirement: Show only verified certifications and do not infer legal guarantees. Trace each assurance statement to its evidence. If a report requires a request, say so; never imply that an unavailable report or a planned control is already verified. Preserve approved content and revise only the parts that fail this check.
Review Your Security and Trust 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.
- Trace each assurance statement to its evidence. If a report requires a request, say so; never imply that an unavailable report or a planned control is already verified.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current security and trust page. Trace each assurance statement to its evidence. If a report requires a request, say so; never imply that an unavailable report or a planned control is already verified. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
