Panels #1
Panels #1
Conversation
| 2. A body | ||
| 3. A footer | ||
|
|
||
| The body contains the content of the panel, the header can be used to add an |
There was a problem hiding this comment.
Please state that header and footer are both optional.
|
|
||
| ## Requirements | ||
|
|
||
| - It must be possible to style the component in any way one likes. |
There was a problem hiding this comment.
Please use a upper-cased must. This improves the readability of the requirements
|
|
||
| ## Constraints | ||
|
|
||
| It is invalid to create an `<span>` with for example the classes `block spread`. |
There was a problem hiding this comment.
Looks like this needs to be removed?
|
|
||
| The component will resize according the size of the device' screen. The options | ||
| that can be part of the header should be handled separately. On small devices | ||
| these options might not be visible correctly but this should be investigated. |
There was a problem hiding this comment.
Depending on the type of options we could add a hamburger like menu? This might work for buttons and dropdown menus.
There was a problem hiding this comment.
I think that is a different pattern, because it has its own behaviour.
waltertamboer
changed the title
| ### How the component will work without color | ||
|
|
||
| * The panel header should have a bigger font size than the panel body. | ||
| * The panel footer should have a smaller font size than the panel body. |
There was a problem hiding this comment.
Border of the panel must have a certain amount of contrast contrasting with the background of the webpage. Else the panel will not be a visible panel for someone with colorblindness.
|
|
||
| ### How the component will enforce any a11y requirements | ||
|
|
||
| No additional comments here. |
There was a problem hiding this comment.
It could contain a description of the inputs that are inside of the panel.
Please review, would love to hear your feedback.