Review:

• oraganization andtemplate were unused (note this is one caveat when a prop is optional, we don't really know if we're even using it. I wonder if there's a lint rule that can help with that, but suffice it to say I just checked which of these the component was de-structuring. Also this is why de-structuringprops is superior to theprop arg...it's helpful to see where everything is being used with a simple find/replace).
• Furthermore, the grouping was odd. I'll add a note about organizing props in our FE V, but essentially, I think what I see in most codebases is alphabetical but mandatory props are grouped in front of optional props. We can also use a different convention, what matters to me is "at a glance" behaviors. Mix-n-match requires more brain power to read.

Review: Will add this to FE V and search for lint rule. zero spaces in HTML markup makes me dizzy!

Review: We forgot to add this story additionally, but now it's here and with two examples. I couldn't think of an example forcontentProps because it's mostly used to inject styles or classes.