Website interaction design
Specify purposeful hover, reveal, scroll, and transition behavior for agreed website elements.
Design files and agreed exports. Implementation is a separate scope.
Once the individual request becomes active. Content readiness and feedback can affect timing.
What you can request
Specify purposeful hover, reveal, scroll, and transition behavior for agreed website elements.
Typical handoff
An approved website interaction design direction, refined for the agreed use and supplied in the formats we confirm in the brief. Editable source files, alternate sizes, or additional versions can be included when agreed at the start.
What to bring
Supply approved copy, brand files, examples, the intended audience, required sizes, and any deadline. We confirm the deliverable and production requirements before starting.
How it fits the partnership
Request this on its own or as a stage within a larger module. We confirm scope and timing, then work through one active request at a time. Related formats and variations are prioritized in the queue rather than assumed to be a single small task.
Typical specifications
Files & handoff. Figma prototype or written interaction specifications; browser implementation only when agreed.
Setup. Scope interface states, triggers, transitions, and responsive behavior for the agreed components.
Limits. Light website interface transitions only. No standalone motion graphics, character animation, animated videos, or 3D effects.
Ready to start
0 of 4 reviewedUse this to prepare your request. We confirm scope and readiness together.
Before this becomes active
Can follow at the agreed stage
- Hosting or domain access when an agreed build or launch stage needs it.
- Minor content refinements; replacing core placeholder content can require rework.
Personal checklist only. Ticks are not saved or sent, and do not start the delivery estimate.
Copying a template does not submit a request.