Docs/feedback #219
Open
Docs/feedback #219
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added layout default
Added missing s in breadcrumb
Removed mix of markdown and html
Removed markdown on headings
Small text edit
Edit to alt text
add anchor link ids
updated on this page anchors
fixed anchor syntax
deleted space
fixed breadcrumb
fixed markdown
remove a space
front matter spaces
removed a breadcrumb
front matter space
remove colon
stray div
remove h5 class
remove space
text edit
added comment
…ystem into docs/feedback
Fixed broken links in On this page
✅ Deploy Preview for design-system-canada-ca ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
Fixed additional typos in the on this page pattern on benefits, insights pages. |
Added text about GC network only
delisma
requested changes
Mar 31, 2023
| <p><strong>Task-based tags</strong> are recommended when analyzing feedback for a group of pages where there are multiple user tasks.</p> | ||
| <p>To identify tasks, ask yourself why the user came to the site. What were they trying to do, or what question were they trying to answer? </p> | ||
| <p><strong>Issue-based tags</strong> may be a better strategy when gathering feedback on a single page, single topic, or where a single task dominates your feedback.</p> | ||
| <p><strong>For large datasets</strong> you may find a second level of tags is needed to add precision. This can be done at the same time you tag the feedback OR when you are ready to analyze a smaller set of feedback.</p> |
There was a problem hiding this comment.
Suggested change
| <p><strong>For large datasets</strong> you may find a second level of tags is needed to add precision. This can be done at the same time you tag the feedback OR when you are ready to analyze a smaller set of feedback.</p> | |
| <p><strong>For large datasets</strong> you may find a second level of tags is needed to add precision. This can be done at the same time you tag the feedback <span class="text-uppercase">or</span> when you are ready to analyze a smaller set of feedback.</p> |
|
|
||
| * Serious implications (financial, legal) | ||
| * Major call driver and/or feedback issue | ||
| * Current media issue OR likely to be a media issue |
There was a problem hiding this comment.
Suggested change
| * Current media issue OR likely to be a media issue | |
| * Current media issue <span class="text-uppercase">or</span> likely to be a media issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
when.md
Fixed broken links in the on this page