notifications-admin/app/templates/views/service-settings/name-local.html

{% extends "withnav_template.html" %}
{% from "components/page-header.html" import page_header %}
{% from "components/page-footer.html" import page_footer %}
{% from "components/form.html" import form_wrapper %}
{% from "components/back-link/macro.njk" import govukBackLink %}

{% block service_page_title %}
  Change your service name
{% endblock %}

{% block backLink %}
  {{ govukBackLink({ "href": url_for('main.service_settings', service_id=current_service.id) }) }}
{% endblock %}
{% block maincolumn_content %}

  {{ page_header('Change your service name') }}

  <p class="govuk-body">Your service name should tell users what the message is about as well as who it’s from. For example:</p>
    <ul class="govuk-list govuk-list--bullet">
      <li>School admissions - {{ current_service.organisation.name or current_user.default_organisation.name }}</li>
      <li>Electoral services - {{ current_service.organisation.name or current_user.default_organisation.name }}</li>
      <li>Blue Badge - {{ current_service.organisation.name or current_user.default_organisation.name }}</li>
    </ul>

  <p class="govuk-body">You should only use an acronym or initialism if your users are already familiar with it.</p>

  <div class="form-group">
    {% if current_service.prefix_sms %}
      <p class="govuk-body">Users will see your service name:</p>
      <ul class="govuk-list govuk-list--bullet">
        <li>at the start of every text message</li>
        <li>as your email sender name</li>
      </ul>
    {% else %}
      <p class="govuk-body">Users will see your service name as your email sender name.</p>
    {% endif %}
  </div>

  {% call form_wrapper() %}
    {{ form.name }}
    {{ page_footer('Save') }}
  {% endcall %}

{% endblock %}