-
Notifications
You must be signed in to change notification settings - Fork 13
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
Challenge Portal Footer #1363
Comments
Work progress document: https://docs.google.com/document/d/1m9GDKig5K_8mTU-F_xMwHaz7KfCrCLLX1_fGh-WqsCc/edit?usp=sharing |
Work done:
Notes: Due to a new branching instruction - a new branch was recreated from eval-main in order to deploy the feature into Eval version. Previous branches were deleted or archived. |
All manual validation passed. |
@jairoanaya Please check appropriate boxes in the Definition of Done list. If some of these items do not apply, please Also, in you earlier comment you mention "Documentation created on Google". What does that mean? |
@r-bartlett-gsa Feedback has been addressed. |
@r-bartlett-gsa All passed testing. The only "issues" are the font and location of Contact Us is slightly off and the GSA Challenge.gov watermark is smaller. |
Scheduled for maintenance. |
@jairoanaya If you are referring to Marni's notes as scheduled for maintenance, please do not work on that at this time. We will address styling and design consistencies at a later time, during fit & finish stage before these updates go live. I consider this story as done. |
Yes. You are correct! I confirm that I will not work on this item at this time. |
Note: This work needs to be deployed to challenge portal eval dev environment (challenge_gov repo > eval main branch)
User Story
As a site user with challenge manager or public solver roles, in order to build my trust using challenge.gov site, I would like to see consistent branding and styling from any page of the site.
Acceptance criteria:
Definition of Done
Doing (dev team)
- [ ] Automated testing has been added or updated in response to changes in this PR- [ ] Database changes have been peer reviewed for index changes and performance bottlenecks- [ ] Automate accessibility tests passed- [ ] Feature toggles if appropriateStaging
Deploy to production (production-like environment for eval capability) (dev team)Production
User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)The text was updated successfully, but these errors were encountered: