Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ticket #1693: Implement "check availability" section on get.gov/domains/choosing/ #269

Merged
merged 42 commits into from
Apr 18, 2024

Conversation

zandercymatics
Copy link
Contributor

@zandercymatics zandercymatics commented Apr 11, 2024

Ticket

Resolves #1693

Changes

  • Adds a check availability module to the domains/choosing page

Context for reviewers

This PR adds a check availability module to the domains/choosing page.

Setup

  1. Click "domains" at the nav bar on the top, then click "Choosing your .gov domain name"
  2. Test the input field and verify it matches with the figma

Code Review Verification Steps

As the original developer, I have

Satisfied acceptance criteria and met development standards

  • Met the acceptance criteria, or will meet them in a subsequent PR
  • Created/modified automated tests
  • Added at least 2 developers as PR reviewers (only 1 will need to approve)
  • Messaged on Slack or in standup to notify the team that a PR is ready for review
  • Changes to “how we do things” are documented in READMEs and or onboarding guide
  • If any model was updated to modify/add/delete columns, makemigrations was ran and the assoicated migrations file has been commited.

Ensured code standards are met (Original Developer)

  • All new functions and methods are commented using plain language
  • Did dependency updates in Pipfile also get changed in requirements.txt?
  • Interactions with external systems are wrapped in try/except
  • Error handling exists for unusual or missing values

Validated user-facing changes (if applicable)

  • New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
  • Checked keyboard navigability
  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)
  • Add at least 1 designer as PR reviewer

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

  • Pulled this branch locally and tested it
  • Reviewed this code and left comments
  • Checked that all code is adequately covered by tests
  • Made it clear which comments need to be addressed before this work is merged
  • If any model was updated to modify/add/delete columns, makemigrations was ran and the assoicated migrations file has been commited.

Ensured code standards are met (Code reviewer)

  • All new functions and methods are commented using plain language
  • Interactions with external systems are wrapped in try/except
  • Error handling exists for unusual or missing values
  • (Rarely needed) Did dependency updates in Pipfile also get changed in requirements.txt?

Validated user-facing changes as a developer

  • New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing

  • Checked keyboard navigability

  • Meets all designs and user flows provided by design/product

  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

  • Tested with multiple browsers, the suggestion is to use ones that the developer didn't (check off which ones were used)

    • Chrome
    • Microsoft Edge
    • FireFox
    • Safari
  • (Rarely needed) Tested as both an analyst and applicant user

Note: Multiple code reviewers can share the checklists above, a second reviewers should not make a duplicate checklist

As a designer reviewer, I have

Verified that the changes match the design intention

  • Checked that the design translated visually
  • Checked behavior
  • Checked different states (empty, one, some, error)
  • Checked for landmarks, page heading structure, and links
  • Tried to break the intended flow

Validated user-facing changes as a designer

  • Checked keyboard navigability

  • Tested general usability, landmarks, page header structure, and links with a screen reader (such as Voiceover or ANDI)

  • Tested with multiple browsers (check off which ones were used)

    • Chrome
    • Microsoft Edge
    • FireFox
    • Safari
  • (Rarely needed) Tested as both an analyst and applicant user

Screenshots

image

@zandercymatics
Copy link
Contributor Author

@rachidatecs Got your suggestions in!

@@ -11,7 +11,42 @@ eleventyNavigation:
title: Choosing your .gov domain name
---


## Start your .gov domain search
Check if the .gov domain you want is available. We'll work with you to find the best domain for your organization that meets our requirements.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zandercymatics can you change that pesky hatch mark to a apostrophe please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

}

successMessage = `
<div class="usa-alert usa-alert--success usa-alert--slim" role="alert">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@zandercymatics I can't believe I'm just now noticing this, but the success and error alerts on this page and on the home page check availability don't use our .gov custom color alerts. Can we make these alerts match the ones on the registrar?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@gabydisarli

This comment was marked as resolved.

@zandercymatics
Copy link
Contributor Author

we have another error message if the person has entered a domain name with invalid characters. Can we add that here?

Hey Gaby, that error message already exists on the page!
image

height: 3.5rem;
}

p {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Blocking: only the last child. Should look like p:last-of-type or similar

pages/domains/domains_choosing.md Outdated Show resolved Hide resolved
_includes/meta.html Outdated Show resolved Hide resolved
@gabydisarli
Copy link
Contributor

@zandercymatics On mobile, the field + text doesn't span the width of the button. Can you make it match? This screenshot is from my iphone 13 but when testing in desktop it seems to "break" at around 401px and below.
IMG_1281

@gabydisarli
Copy link
Contributor

Can I get a content update too? After chatting with Katherine we agreed it would be great to update the text on the card on /domains to point to this new feature. Can we change the body text of the card to:

Check if a domain is available and read name requirements for your organization

@gabydisarli
Copy link
Contributor

Caught another errant hatch mark 🙃

Screenshot 2024-04-18 at 10 36 49 AM

@gabydisarli gabydisarli self-requested a review April 18, 2024 16:34
Copy link
Contributor

@gabydisarli gabydisarli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@zandercymatics zandercymatics merged commit 6c4b27b into main Apr 18, 2024
4 checks passed
@zandercymatics zandercymatics deleted the za/1693-implement-check-availability-section branch April 18, 2024 16:35
@zandercymatics zandercymatics restored the za/1693-implement-check-availability-section branch May 3, 2024 20:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement "check availability" section on get.gov/domains/choosing/
4 participants