wiki/clients/current/didion/2025-11-03-event-page-revisions.md · 392 words · 2025-11-03
Event Page Revisions — 2025-11-03
Overview
During the [1], Melissa and Michał reviewed the Didyna event page design. The client's core directive was simplicity — the existing design was too complex and did not match the reference sample provided. Michał was tasked with completing revisions the same morning so the page could be approved and built immediately.
Context
The client (Didyna) provided a reference sample and supporting materials after the initial wireframe had already been created. As a result, the wireframe did not reflect the client's actual direction. The revision session was used to align the design with the client's provided assets and feedback.
Required Revisions
- Replace the existing form with the client-provided "claim pull tab" form.
- Change any instance of "snack meal" to "corn masa" (e.g., "What is your annual corn masa volume?").
Prizes
- Display exactly two prizes:
1. The client's bottle (asset provided by client).
2. A Visa gift card graphic (source a standard graphic).
- Remove any third prize placeholder — a third prize has not been confirmed.
Steps Section
- Add headline: "Follow these four easy steps."
- Remove all descriptive body copy below the step headers — keep only the step titles (e.g., "Submit your entry," "Stop by," "Get a pull," "Win").
Visuals / Graphics
- Use the client's "cheesy" pull tab art and provided graphics to match their sample aesthetic.
- The client's sample was intentionally low-fi; do not over-polish the visual treatment.
- Do not spend excessive time on the hero/background visual — move quickly and submit for feedback.
Timeline & Handoff
| Step |
Owner |
Timing |
| Complete design revisions |
Michał |
Morning of 2025-11-03 |
| Submit to client for approval |
Melissa |
Same day |
| Build page |
Eshock |
Immediately after approval |
Notes
- Melissa noted that Eshock's availability was needed for same-day build — confirm before sending for approval.
- Mark had not yet reviewed the broader Asymmetric project; Melissa planned to remind him in a separate meeting.
- The client's reference sample was described as "horrible" aesthetically, but the team agreed to match it rather than redesign — client alignment takes priority.