Write a bug report another developer can reproduce.
A useful bug report reduces the distance between seeing a problem and understanding it. A dramatic title cannot replace a reproducible example.
Read the guidePractical craft for people building for the web.
Explore DevelopmentCategory
Themes, tools, workflows, and practical ideas: original Development guides for people building for the web.
A useful bug report reduces the distance between seeing a problem and understanding it. A dramatic title cannot replace a reproducible example.
Read the guideA header and a content section can each look reasonable while failing to line up together. Shared alignment rules prevent that subtle visual drift.
Hover is a convenience for some users, not a complete interaction model. A menu needs an explicit way to open, close, and move through its links.
A page can feel heavy even when its JavaScript is small. Large images deserve attention before decorative motion becomes the focus of a performance pass.
A reviewer needs to understand the problem, the change, and the evidence that it works. A large diff becomes easier only when its purpose stays clear.
No results is a normal state in a search interface. It should explain the current situation without blaming the reader or pretending something broke.
A release checklist should direct attention to what could fail. Repeating every possible check for every change can make the important ones easier to miss.
A tool deserves attention when it solves a recurring problem. A long feature list is less useful than one improvement you can describe and verify.
Cards rarely receive equally sized titles and descriptions. Designing only with balanced dummy text hides the problems that appear after real publishing begins.
Related topics