4.x - CTA

[bspeare]

Resolves https://github.com/uiowa/uids/issues/782. Resolves https://github.com/uiowa/uids/issues/897.

[pyrello]

I guess I had missed that this was in progress and was so far along. Nice work on this so far. I think we need to refine how we are thinking about the variations (what is changing) and possibly split the properties to reflect that, but otherwise this is looking really good.

[pyrello]

Some thoughts for next steps after this:

• Implementing properties (headline_style) on components (CTA, Card) for nested components (Headline) doesn't scale very well. That is, it introduces a lot of redundancy because each component that implements a property to pass through to the nested component has to have essentially the same property as the nested component. For the headline example, this means that every component that implements the headline component needs to have a headline_text_style, headline_underline, and headline_highlight property that is the same as the relevant properties on the headline component. If we make changes to the logic of how the headline component works, we have to propagate those changes throughout all the parent component properties as well.
• I think we can resolve this by doing something like what we did with backgrounds, where we created a shared resource that can be pulled into a component. If there are logical changes, then we update them in the shared resource and they are propagated to every place where they are implemented.
• We'll probably need a way to only pull in the properties we need for a given component. There may be valid reasons why we want to hardcode/restrict some options in a nested component, so we don't want to have to accept them as all or nothing.