Errors that keep their context
Return useful errors from the place where something failed, and handle them where a decision can be made.
Read the guideBuild a little. Understand a little more.
Practical guides to Go, HTML, and CSS.
Start with the standard library.
Write meaningful HTML.
Let the browser do its job.
Start with the standard library. Add a route, return JSON, and give every request a sensible time limit.
Build your first endpoint ↗Return useful errors from the place where something failed, and handle them where a decision can be made.
Read the guideUse httptest to verify the contract a caller sees: status, headers, and response data.
Read the guideA practical document outline with landmarks, headings, and links that still works before you add CSS.
Read the guideLabels, input types, and useful validation are a better starting point than a clever floating placeholder.
Read the guideSet dimensions, describe the useful content, and let the browser pick an appropriately sized source.
Read the guideLet the available space decide the number of columns, then use media queries for the exceptions.
Read the guideLine length, line height, and spacing do more for a reading page than a long list of fonts.
Read the guideMake keyboard navigation visible without making every mouse click look like an error.
Read the guide