Skip to content
This repository has been archived by the owner on Sep 24, 2022. It is now read-only.

Update writing-tips.md #187

Merged
merged 1 commit into from
Jan 21, 2022
Merged

Conversation

aidanatwork
Copy link
Contributor

@aidanatwork aidanatwork commented Feb 24, 2021

Purpose / why

Improves first bullet for Writing Procedures.

What changes were made?

Adapted language from the base template on chunking procedural steps, removed the reference to usability studies (there is not sufficient credible research on this topic). Fixes templates issue #68: #68.

Verification

To verify, read the new first bullet point I've added to "Writing Procedural Steps" and decide if it fixes the issue.


Checklist

Pull-request reviewer should ensure the following

  • Are issues linked correctly?
  • Is this PR labeled correctly?
  • If template updates: do they align with developers.google.com/style/?
  • Did the PR receive at least one 👍 and no 👎 from core-maintainers?
  • On merging, did you complete the merge using keywords?
  • On merging, did you add any applicable notes to a draft release and link to this PR?

Adapted language from the base template on chunking procedural steps, removed the reference to usability studies (there is not sufficient credible research on this topic). Fixes templates issue #68: #68. To verify, read the new first bullet point I've added to "Writing Procedural Steps" and decide if it fixes the issue.
@camerons
Copy link
Member

This text is good, and I'd merge this request, except for the fact that I've just moved the base template from the incubator to the templates repository, and this fix won't be copied across

Would you mind re-applying to the templates repository, dev branch, once this PR has landed: #190

Copy link
Contributor

@barbaricyawps barbaricyawps left a comment

Choose a reason for hiding this comment

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

@aidanatwork , this looks great. I made a minor, non-blocking suggestion.

@@ -17,7 +17,7 @@ Follow these writing guidelines when developing content using the templates avai

Here are some recommendations you can use when creating procedural steps:

* Usability studies show that procedures should not be more than seven primary steps long.
* For procedures with numerous steps, consider "chunking" content into sub-sections of 5-10 steps. It makes the information easier to read and remember, and gives the reader a sense of accomplishment after each chunk is completed. Chunking is recommended by major companies, such as in [Microsoft's writing style guide](https://docs.microsoft.com/en-us/style-guide/procedures-instructions/writing-step-by-step-instructions#complex-procedures), and from the Nielsen Norman Group's [research on chunking and usability](https://www.nngroup.com/articles/short-term-memory-and-web-usability/).
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggestion (non-blocking): Rather than putting the word chunking in quotation marks, how about italics to indicate you're introducing a new term?

@mgan59 mgan59 changed the base branch from master to main June 16, 2021 22:01
@mgan59
Copy link
Contributor

mgan59 commented Jun 16, 2021

@aidanatwork I moved the repository to dev and changed the base branch on this PR. If you end up pushing additional changes be aware as it may require a rebase.

@mgan59 mgan59 changed the base branch from main to dev June 16, 2021 22:04
@barbaricyawps barbaricyawps merged commit 7450e8c into dev Jan 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants