Define motion approach for Site Starter

[stephaniefois]

Overview

Drawing from our motion tiers outlined by the Motion Working Group, we will need to define:

• What tier of motion is right for Site Starter?
• Which native browser features or APIs can be leveraged for Wordpress?
• What does implementation look like for Wordpress?
• Who else from the Site Starter team may be required for planning and implementation?

[nathanlong]

We discussed this very briefly in our last UI Standup, some of the general points:

1. WP will be harder to animate than Craft because of lack of control over markup. This might mean that general patterns can only set to a coarser level (entire block vs inner elements) up front.
2. Possibility of creating 'recipes' over direct implementation to allow choice in project setup.
3. General consensus was to not include GSAP by default, but that the tipping point to including it is lower than we think.
4. Focus on general global patterns (animate on scroll, number count-up, etc)

@nathan-schmidt-viget Has also had experience integrating motion onto our site starters.

[nathan-schmidt-viget]

After working on the first pass of adding motion to SAC we can animate inner elements up to a point. It gets harder when we want to animate individual text/letters/button items in a content block. But animating the whole group that wraps the content, (such as fade-in) would be very doable.

Here is a more complex example of some GSAP animation on a block for SAC: