app/templates/components/sms-message.html

{% macro sms_message(body, recipient) %}
  <div class="sms-message">
    <div class="sms-message-wrapper">
      {{ body|placeholders }}
    </div>
  </div>
  {% if recipient %}
    <p class="sms-message-recipient">
      {{ recipient }}
    </p>
  {% endif %}
{% endmacro %}

{% macro message_status(status, time) %}
  <div class="sms-message-history">
    <p class="sms-message-history-heading">
      {{ status }} <span class="sms-message-history-heading-time">{{ time }}</span>
    </p>
  </div>
{% endmacro %}
Try out previewing messages 2015-12-11 12:02:21 +00:00			`{% macro sms_message(body, recipient) %}`
Add GOV.UK Elements as a submodule Since GOV.UK Elements is versionned now it makes sense to bring it in as a dependency. This enforces a separation between what generic stuff we’re using from Elements and what is specific to our app. The benefit is that when the generic stuff changes it will be easy to bring those changes in. This commit also bumps GOV.UK frontend toolkit to the latest version (v4.5.0). 2015-12-10 16:52:45 +00:00			`<div class="sms-message">`
			`<div class="sms-message-wrapper">`
			`{{ body\|placeholders }}`
			`</div>`
			`</div>`
Remove log of activity from single notification Having the full history of the message is more information than is necessary. We should only show what stage the message is at, and the time that it reached that stage. We can do research later on to find out if users understand or care about the different stages. 2015-12-18 17:03:49 +00:00			`{% if recipient %}`
			`<p class="sms-message-recipient">`
			`{{ recipient }}`
			`</p>`
			`{% endif %}`
Add GOV.UK Elements as a submodule Since GOV.UK Elements is versionned now it makes sense to bring it in as a dependency. This enforces a separation between what generic stuff we’re using from Elements and what is specific to our app. The benefit is that when the generic stuff changes it will be easy to bring those changes in. This commit also bumps GOV.UK frontend toolkit to the latest version (v4.5.0). 2015-12-10 16:52:45 +00:00			`{% endmacro %}`
Add message history 2015-12-17 14:58:37 +00:00
Remove log of activity from single notification Having the full history of the message is more information than is necessary. We should only show what stage the message is at, and the time that it reached that stage. We can do research later on to find out if users understand or care about the different stages. 2015-12-18 17:03:49 +00:00			`{% macro message_status(status, time) %}`
			`<div class="sms-message-history">`
			`<p class="sms-message-history-heading">`
			`{{ status }} <span class="sms-message-history-heading-time">{{ time }}</span>`
			`</p>`
			`</div>`
Add message history 2015-12-17 14:58:37 +00:00			`{% endmacro %}`