- #99
- #98
- #97
- #96
- #95
- #94
- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
Avoid boring documentation, Add interactivity to it
Adding interactivity to documents to avoid monotony, there are some details or niche requirements in website planning that are easily forgotten, and it’s always too late when the problem is discovered. For example:
- Multilingual support
- Page Meta information
- Complete UI component states
- …
Therefore, writing a checklist makes it easy to quickly verify or help newcomers get started, but such documents are often only looked at a few times before no one revisits them 😅. Who likes to flip through documents for no reason!
Instead of “suggesting” to check document A when performing action A, perhaps creating an SOP checklist without unnecessary words, following the “required” process, might lead to a greater sense of accomplishment and accuracy. The Checklist Design website has many excellent SOP documents, such as best practices for components, pages, or designs.
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1