Feature/callout documentation

[klepas]

Description

Adds basic (missing) documentation for the existing (and three new) callouts under the Patterns section.

When merged this should fix for https://github.com/AusDTO/dto-design-guide/issues/119

That issue holds the bulk of the bg info.

Happy to leave this PR open for Jools to work on, or we could merge and ensure Jools sees it when he comes back — undoubtedly there’s content debt here that we will want to fix…

Additional information

Screenshot:

Definition of Done

• [ ] Content/documentation reviewed by Jools or someone in the #content-design team
• [ ] UX reviewed by Gary or someone the Design team
• [ ] Code reviewed by one of the core developers
• [x] Acceptance Testing
  • [x] HTML5 validation (CircleCI)
  • [x] Accessibility testing & WCAG2 compliance
• [ ] Stakeholder/PO review

[AndrewArch]

maybe we could consider a brighter green for 'success' (eg #008000) in a future release?

[klepas]

maybe we could consider a brighter green for 'success' (eg #008000) in a future release?

@AndrewArch yea, happy to when we revisit colours in 2.x. At the moment this colour ($success-green) is setup and shared in a bunch of other places, namely forms.

[joolswood]

Hey @dominikwilkowski and @klepas I don't think this is in the right place. I think what we've got are code and examples for a component called "callouts".

When we provide guidance and examples of how these components are used as part of a service to help the user then that content should go in Patterns. But I don't think we'll get to this until 2.0.

So I'd like to move this content to the Components collection and do some work on the lead-in and examples.

[klepas]

So I'd like to move this content to the Components collection and do some work on the lead-in and examples.

@joolswood I however want to close #119 now, and add a new issue assigned to you if you want to move this within the 1.x documentation site.