A useful website resource should answer the question in front of you. If a form cannot be completed with a keyboard, another page of colour inspiration is not the next step. If a WordPress update fails, a new layout will not restore the database. This collection is organised around work you can actually verify.
Goodie is an independent web-design journal. Historic credits pointing to this domain do not mean the current publication designed those websites or provides the former agency’s services.
Before changing a WordPress site
Start with the WordPress backup documentation. It distinguishes the database from the files: both belong in a recovery plan. A copy of a theme does not contain the articles stored in the database, and a database export does not contain uploaded images.
A practical next step is to identify a complete backup set and where it can be restored. Record its date and scope. Do this before an update, rather than discovering afterwards that the only saved file is a screenshot of the old homepage.
When software needs updating
The official update guide explains the update process and compatibility checks. It does not prescribe a single universal order for every plugin, theme and WordPress version. Read the relevant release notes where dependencies matter.
After an update, check a real task: submitting an enquiry, opening an article, using search or completing the site’s actual primary action. A successful update message and a working customer journey are different observations.
When images need to be understandable
The W3C image tutorials distinguish informative, decorative and functional images. The useful question is what the image contributes in its context. An icon inside a link may need an accessible name describing the destination or action, rather than a description of its shape.
For a portfolio, consider a screenshot that demonstrates a layout. A caption can explain the design decision; alternative text should serve the purpose of the image in that article. Repeating a long caption word for word is not automatically the most useful solution.
When a page feels slow
web.dev’s performance course is a starting point for understanding loading and responsiveness. Use it to investigate a specific symptom instead of treating a score as the whole experience.
For example, compare the image requested on a narrow screen with the size at which it is displayed. Then check whether a change reduces transferred bytes without making the image visibly unsuitable. Keep the page, device conditions and measurement method consistent enough for the comparison to mean something.
Turn a resource into a small work plan
- Write the observable problem in one sentence.
- Choose the source that addresses that problem.
- Make one reversible change with a saved starting point.
- Repeat the relevant task or measurement.
- Record what improved, what did not and what remains uncertain.
That sequence is deliberately modest. It turns documentation into a decision you can review. A longer list of tools is less valuable than a short record showing which change solved the problem and why you believe it did.