From 96142b35d0779133ea552f3984cdf525d55d81c7 Mon Sep 17 00:00:00 2001 From: Christopher Bennage Date: Sun, 11 Feb 2018 18:15:25 -0800 Subject: [PATCH] an initial take on checklist contribution --- docs/checklist/_contributors.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 docs/checklist/_contributors.md diff --git a/docs/checklist/_contributors.md b/docs/checklist/_contributors.md new file mode 100644 index 00000000000..2bebd83d44c --- /dev/null +++ b/docs/checklist/_contributors.md @@ -0,0 +1,21 @@ +# Contributing to Checklists + +## Recommend structure +An item in a checklist should include these elements: +1. A concise actionable statement. +2. An explanation of why the statement is relevant to the domain of the checklist. +3. A recommendation for how to address the statement. +4. A list of additional related resources. + +## Example + +``` markdown +### Ensure that all checklist items are consistent + +A consistent structure helps readers better navigate the guidance. By applying these rules to all checklist items we maintain a higher level of quality. The standard structure makes it easier for others to contribute. + +_We recommend using the standard format for all checklist items. If an item doesn't fit the structure, exceptions should be discussed and approved by the content development team._ + +* [The Checklist Manifesto](http://atulgawande.com/book/the-checklist-manifesto/) by Atul Gawande +* [Design Review Checklists](../index.md) +``` \ No newline at end of file