mirror of
https://github.com/GSA/notifications-admin.git
synced 2026-07-31 20:00:00 -04:00
75c92c12c1
If the templates page contains text messages and emails then there’s two ways it could be structured: - into two sections, all text messages first, then all emails - emails and text messages interleaved, sorted by date I think the second one is better. Imagine a situation where you mostly do emails but have a few text messages. You’d have to scroll past the text messages to get to your emails. Every time. I reckon that the most commonly accessed templates will be the most recent ones.
54 lines
881 B
SCSS
54 lines
881 B
SCSS
.sms-message {
|
|
|
|
position: relative;
|
|
margin: 0 0 $gutter 0;
|
|
|
|
&:before {
|
|
content: '';
|
|
position: absolute;
|
|
z-index: 10;
|
|
bottom: -12px;
|
|
right: 5px;
|
|
width: 20px;
|
|
height: 25px;
|
|
border-radius: 100%;
|
|
background: $panel-colour;
|
|
}
|
|
|
|
&:after {
|
|
content: '';
|
|
position: absolute;
|
|
z-index: 20;
|
|
bottom: -15px;
|
|
right: -5px;
|
|
border-radius: 100%;
|
|
width: 20px;
|
|
height: 20px;
|
|
background: $white;
|
|
}
|
|
|
|
&-wrapper {
|
|
width: 100%;
|
|
display: inline-block;
|
|
box-sizing: border-box;
|
|
position: relative;
|
|
z-index: 30;
|
|
padding: $gutter/2;
|
|
background: $panel-colour;
|
|
border-radius: 5px;
|
|
white-space: normal;
|
|
}
|
|
|
|
&-recipient {
|
|
@include copy-19;
|
|
color: $secondary-text-colour;
|
|
margin: -$gutter-half 0 $gutter 0;
|
|
}
|
|
|
|
&-name {
|
|
@include bold-19;
|
|
margin: 50px 0 10px 0;
|
|
}
|
|
|
|
}
|