Change <a> style

This commit is contained in:
zandercymatics 2024-04-26 12:06:20 -06:00
parent 1ea4b0b6f5
commit 9daa6ddafe
No known key found for this signature in database
GPG key ID: FF4636ABEC9682B7

View file

@ -9,7 +9,7 @@
<p>
Once a domain request has been adjudicated, the details of that request should not be modified.
To update attributes (like an organizations name) after a domains approval,
go to <a href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>.
go to <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>.
Similar fields display on each Domain page, but edits made there will not affect the corresponding domain request.
</p>
{% elif opts.model_name == 'domaininformation' %}
@ -17,7 +17,7 @@
Domain information represents the basic metadata for an approved domain and the organization that manages it.
It does not include any information specific to the registry (DNS name servers, security email).
Registry-related information
can be managed within the <a href="{% url 'admin:registrar_domain_changelist' %}">Domains</a> table.
can be managed within the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a> table.
</p>
<p>
@ -25,7 +25,7 @@
</p>
<p>
Domain information is similar to <a href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a>,
Domain information is similar to <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a>,
and the fields are nearly identical,
but edits made to one are not made to the other.
Domain information exists so we dont modify details of an approved request after adjudication
@ -46,7 +46,7 @@
<p>
If an invitation is created in this table, an email will not be sent.
To have an email sent, go to the domain in <a href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>,
To have an email sent, go to the domain in <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>,
click the “Manage domain” button, and add a domain manager.
</p>
{% elif opts.model_name == 'contact' %}
@ -54,7 +54,7 @@
Contacts include anyone who has access to the registrar (known as “users”) and anyone listed in a domain request,
including other employees and authorizing officials.
Only contacts who have access to the registrar will have
a corresponding record within the <a href="{% url 'admin:registrar_user_changelist' %}">Users</a> table.
a corresponding record within the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_user_changelist' %}">Users</a> table.
Updating someones contact information here will not affect that persons Login.gov information.
</p>
{% elif opts.model_name == 'logentry' %}
@ -63,7 +63,7 @@
The table on this page is useful for searching actions across all records.
To understand what happened to an individual record (like a domain request),
its better to go to that specific page
(<a href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a>) and click on the “History” button.
(<a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a>) and click on the “History” button.
</p>
{% elif opts.model_name == 'domain'%}
<p>
@ -100,7 +100,7 @@
<p>
This table does not include “alternative domains,”
which are housed in the <a href="{% url 'admin:registrar_website_changelist' %}">Websites</a> table.
which are housed in the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_website_changelist' %}">Websites</a> table.
</p>
{% elif opts.model_name == 'host' %}
<p>
@ -111,7 +111,7 @@
<p>
In general, you should not modify these values here. They should be updated directly inside the registrar.
To update a domains name servers and/or IP addresses,
in the registrar, go to the domain in <a href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>,
in the registrar, go to the domain in <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domain_changelist' %}">Domains</a>,
then click the "Manage domain" button.
</p>
{% elif opts.model_name == 'publiccontact' %}
@ -152,7 +152,7 @@
{% elif opts.model_name == 'usergroup' %}
<p>
Groups are a way to bundle admin permissions so they can be easily assigned to multiple users.
Once a group is created, it can be assigned to people via the <a href="{% url 'admin:registrar_user_changelist' %}">Users</a> table.
Once a group is created, it can be assigned to people via the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_user_changelist' %}">Users</a> table.
</p>
<p>
@ -174,7 +174,7 @@
<p>
Each user record displays the associated “contact” info for that user,
which is the same info found in the <a href="{% url 'admin:registrar_contact_changelist' %}">Contacts</a> table.
which is the same info found in the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_contact_changelist' %}">Contacts</a> table.
Updating these details on the user record will also update the corresponding contact record for that user.
</p>
{% elif opts.model_name == 'verifiedbystaff' %}
@ -194,8 +194,8 @@
</p>
<p>
This does not include any “requested domains” that have appeared within the <a href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a> table.
Those names are managed in the <a href="{% url 'admin:registrar_draftdomain_changelist' %}">Draft domains<a/> table.
This does not include any “requested domains” that have appeared within the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_domainrequest_changelist' %}">Domain requests</a> table.
Those names are managed in the <a class="usa-button usa-button--unstyled text-underline" href="{% url 'admin:registrar_draftdomain_changelist' %}">Draft domains<a/> table.
</p>
{% else %}
<p>This table does not have a description yet.</p>