Add information architecture heuristics to process documentation #704
Conversation
This file contains hidden or 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
This commit adds an IA heuristics page to our process documentation. The NGINX DocOps teams spends a lot of time engaged with IA and is increasingly involved with using heuristics to assess content. This gives us a baseline of shared parameters and vocabulary for efforts going forward.
✅ Deploy Preview will be available once build job completes!
|
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.
Proposed changes
This pull request adds a document describing ten information architecture heuristics that can be used to assess information architecture and overall content design. It is an adaptation of work by Abby Covert.
This document does not include rating criteria, which tend to be subjective - these are largely intended for discussion and planning points. Assigning ratings can be handled separately as part of a prescriptive process for managing information architecture.
There will likely be follow up work to point to live examples to illustrate individual heuristics.
Checklist
Before merging a pull request, run through this checklist and mark each as complete.
README.mdandCHANGELOG.mdFootnotes
Potentially sensitive changes include anything involving code, personally identify information (PII), live URLs or significant amounts of new or revised documentation. Please refer to our style guide for guidance about placeholder content. ↩