app/templates/components/tick-cross.html

{% macro tick_cross(yes, label, truthy_hint='Can', falsey_hint='Cannot') %}
  <li>
    {% if yes %}
      <span class="tick-cross-tick">
        <span class="visually-hidden">{{ truthy_hint }}</span>
        {{ label}}
      </span>
    {% else %}
      <span class="tick-cross-cross">
        <span class="visually-hidden">{{ falsey_hint }}</span>
        {{ label}}
      </span>
    {% endif %}
  </li>
{% endmacro %}

{% macro tick_cross_done_not_done(yes, label) %}
  {{ tick_cross(yes, label, truthy_hint='Done: ', falsey_hint='Not done: ') }}
{% endmacro %}
Replace can't with cannot 2019-09-12 16:45:39 +01:00			`{% macro tick_cross(yes, label, truthy_hint='Can', falsey_hint='Cannot') %}`
Tidy layout of team page The team page was a bit of a mess: - invited and active tables didn’t line up - lots of things were wrapping onto two lines - the empty fields for when a user didn’t have permissions looked broken This commit splits each row of the table (not actually a table any more) onto two lines. First line has the user’s info, second has their permissions and any associated actions. 2016-07-07 09:17:50 +01:00			`<li>`
			`{% if yes %}`
			`<span class="tick-cross-tick">`
Check for team members on request to go live page One of the things that we want to check before a service goes live is that they have at least two team members with the manage service permission. Anyone who can make a request to go live has this permission, so that means one additional user is needed. This is what we can automatically communicate to the user. Under the hood this makes use of the logic added in https://github.com/alphagov/notifications-admin/pull/1891 2018-02-27 11:33:26 +00:00			`<span class="visually-hidden">{{ truthy_hint }}</span>`
Tidy layout of team page The team page was a bit of a mess: - invited and active tables didn’t line up - lots of things were wrapping onto two lines - the empty fields for when a user didn’t have permissions looked broken This commit splits each row of the table (not actually a table any more) onto two lines. First line has the user’s info, second has their permissions and any associated actions. 2016-07-07 09:17:50 +01:00			`{{ label}}`
			`</span>`
			`{% else %}`
			`<span class="tick-cross-cross">`
Check for team members on request to go live page One of the things that we want to check before a service goes live is that they have at least two team members with the manage service permission. Anyone who can make a request to go live has this permission, so that means one additional user is needed. This is what we can automatically communicate to the user. Under the hood this makes use of the logic added in https://github.com/alphagov/notifications-admin/pull/1891 2018-02-27 11:33:26 +00:00			`<span class="visually-hidden">{{ falsey_hint }}</span>`
Tidy layout of team page The team page was a bit of a mess: - invited and active tables didn’t line up - lots of things were wrapping onto two lines - the empty fields for when a user didn’t have permissions looked broken This commit splits each row of the table (not actually a table any more) onto two lines. First line has the user’s info, second has their permissions and any associated actions. 2016-07-07 09:17:50 +01:00			`{{ label}}`
			`</span>`
			`{% endif %}`
			`</li>`
			`{% endmacro %}`
Check for team members on request to go live page One of the things that we want to check before a service goes live is that they have at least two team members with the manage service permission. Anyone who can make a request to go live has this permission, so that means one additional user is needed. This is what we can automatically communicate to the user. Under the hood this makes use of the logic added in https://github.com/alphagov/notifications-admin/pull/1891 2018-02-27 11:33:26 +00:00
			`{% macro tick_cross_done_not_done(yes, label) %}`
			`{{ tick_cross(yes, label, truthy_hint='Done: ', falsey_hint='Not done: ') }}`
			`{% endmacro %}`