Kinetic Event Title Design Prompt

Create an HTML/CSS/JavaScript interaction study with explicit start, active and completed states and a readable prefers-reduced-motion fallback for [PROJECT] and [AUDIENCE]. The task is: Kinetic Event Title.

Required content and structure

Animate an event title, date and venue through a short legible typographic sequence.

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: white, charcoal and vivid green highlights; clearly labeled start, transition and end states. 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 exact event title, date, venue, sequence length and final static frame. Identify the longest piece of text viewers must read.

Layout and behavior

Use typography in a short sequence with clear holds between movements. Keep logistics stable long enough to be understood rather than animating every word continuously.

Task-specific acceptance check

• Keep exact event facts visible long enough to read and offer a static frame.
• Time the sequence at normal speed and inspect its final frame.
• Reduced-motion viewers should receive the complete event information without waiting through the animation.

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.

Make the complete information and action available without animation. Provide pause or dismissal where relevant. Document triggers and transitions; do not replace actual progress with a decorative timer.

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 Kinetic Event Title. 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: Animate an event title, date and venue through a short legible typographic sequence. Use the following task-specific layout guidance when translating the image into editable elements: Use typography in a short sequence with clear holds between movements. Keep logistics stable long enough to be understood rather than animating every word continuously.

Visual direction from the example brief

white, charcoal and vivid green highlights; clearly labeled start, transition and end states.

Output and editability

Recreate the finished graphic as editable text, shapes and image layers. The reference is a composition, not an editor interface; do not add navigation, forms or dashboard widgets that are absent from it. Use typography in a short sequence with clear holds between movements. Keep logistics stable long enough to be understood rather than animating every word continuously. Confirm intended dimensions and preserve text hierarchy when adapting the artwork. Keep exact event facts visible long enough to read and offer a static frame.

Visual comparison and delivery

1. 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.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. 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.