"Enablement" block no longer has design
Priority: Low/Medium/High (choose one, remove the other options)
Issue Description:
"Enablement" block no longer has specific formatting so it looks out of place.
Suggested Resolution
@scottbuscemi I'm not sure which block you're referring to. But it might have been solved with https://github.com/pantheon-systems/documentation/issues/8815 and https://github.com/pantheon-systems/documentation/pull/9074
Can you check?
This isn't resolved. The <Enablement> block has no formatting so it seems like a random header/paragraph in the middle of a doc.
Ah, I understand now. @mel-miller I don't know that we need a separate Enablement React component in addition to the Alert React component.
The Enablement component does not include anything the from pds: https://github.com/pantheon-systems/documentation/blob/main/src/components/enablement/index.js
The Alert component does. https://github.com/pantheon-systems/documentation/blob/main/src/components/alert/index.js
I think the appropriate resolution here is for me to make a PR that either
- Deletes the
Enablementcomponent and replaces all usages with theAlertcomponent and sets the type toinfo. - Updates the
Enablementcomponent to use theCalloutcomponent frompdsand hard codes the type toinfo.
I think option 2 is better as it will make it easier to preserver the analytics tracking present in the Enablement component now. Though I should double check that anyone is is checking those analytics.
@rachelwhitton since you're working more closely with a design system update right now, can you take this issue?