BP
BP
Here is the [draft](https://docs.google.com/document/d/1qxDQhPfCVuNEhSnP9xUc0kMEEkM-OC28Us2RlQp0h8Y/edit#) in progress on this issue
It looks like USWDS has a "return to top" component in their [footers](https://designsystem.digital.gov/components/footer/) that we could maybe use for this.
I'm going to remove the piece about value statements for now. I messaged the #wg-user-research-compensation a few weeks ago while looking into this for login and got crickets. I think...
@jstrothman yes that makes sense based on your note and the above acceptance criteria.
Talking with former product owner of the ux guide in the alumni slack - "There was no rhyme or reason to making them part of the repo vs part of...
@jstrothman I went with changing the language directly in the file. My rationale being its easier for 18F folks to find as they read. If we move the files to...
I moved the content from the previous draft [into this doc](https://www.google.com/url?q=https://docs.google.com/document/d/1Z6CWkmLRwDA_6L2h4EE7tUrFL5M39CalC86UG06OBqg/edit?usp%3Dsharing&sa=D&source=docs&ust=1670441426266074&usg=AOvVaw3TJb82Qa97i4jCfsGA05D8) that shows the content throughout sections of the guide that already exist to see if we could have this...
Closing this issue. Superseded by issue #308 Update recruitment and compensation sections and #309 add content to Debrief section
@MelissaBraxton FYI - I created [Recruiting with communities and nonnative English speakers#320](https://github.com/18F/ux-guide/issues/320) to address your comment.