app/templates/components/sms-message.html

{% macro sms_message(body, recipient=None, name=None, edit_link=None) %}
  {% if name %}
    <h3 class="sms-message-name">
      {% if edit_link %}
        <a href="{{ edit_link }}">{{ name }}</a>
      {% else %}
        {{ name }}
      {% endif %}
    </h3>
  {% endif %}
  <div class="sms-message">
    <div class="sms-message-wrapper">
      {{ body|placeholders }}
    </div>
  </div>
  {% if recipient %}
    <p class="sms-message-recipient">
      {{ recipient }}
    </p>
  {% endif %}
{% endmacro %}
Add some SMS messages to the choose template page 2016-01-13 16:21:29 +00:00			`{% macro sms_message(body, recipient=None, name=None, edit_link=None) %}`
			`{% if name %}`
			`<h3 class="sms-message-name">`
			`{% if edit_link %}`
Add a prototype email template 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. 2016-01-13 16:27:54 +00:00			`<a href="{{ edit_link }}">{{ name }}</a>`
			`{% else %}`
			`{{ name }}`
Add some SMS messages to the choose template page 2016-01-13 16:21:29 +00:00			`{% endif %}`
			`</h3>`
			`{% 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			`<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 %}`