Build a kit that works at small sizes
Gather a logo or clean wordmark, a light-background version, a dark-background version if needed, and a square mark only if it remains recognizable. Test each at the size it will appear in a phone header. Fine detail that looks impressive on a large presentation may disappear on the website.
For a fictional furniture restorer, a simple wordmark and one recognizable symbol may be enough for launch. The owner checks that the business name remains readable on an invoice, a small browser view, and a project photo credit. Keep source files as well as common image exports so future designers can make useful changes without rebuilding the identity.
Our recommended asset index records filename, purpose, approved version, owner, and any usage restriction. Avoid names such as final-final-new. A descriptive name with a date or version makes handoffs less ambiguous. Retire old versions into a clearly labeled folder so they are not chosen accidentally.
Choose colors and images for communication
W3C's design guidance addresses contrast and avoiding color as the only way to communicate information. Use those principles when testing the palette in real buttons, body text, links, and form states. A color swatch alone cannot demonstrate whether a finished page is easy to read.
Choose a few images that answer customer questions. The furniture restorer might show an actual workspace, an approved before-and-after pair, and the person customers will meet. Add context explaining what each project demonstrates. Obtain the necessary permission before publishing identifiable people or customer property. Do not present a stock workshop as your own premises.
Make a shot list before taking photos: subject, purpose on the page, orientation, and any detail to keep visible. Leave room around the subject so the image can be cropped for different screens. Preserve originals, then create web-ready versions as part of the build process.
Prepare image descriptions and a handoff note
W3C's image guidance distinguishes informative, decorative, and functional images when choosing text alternatives. Give the website builder the intended purpose of each image; that context helps them implement the appropriate alternative text instead of repeating a filename.
For the restoration example, a project image could be accompanied by a plain description of the repaired chair and work performed. A decorative background does not need to carry the service explanation. Keep essential service details in ordinary page text so they remain available even when an image is cropped or not displayed.
Finish with a one-page usage note: approved business name, logo variants, color values, typography choices, image locations, and the person who approves new material. This compact kit supports a coherent first website without turning a small launch into an open-ended branding exercise.
Your practical checklist
- Test the business name and logo at phone-header size.
- Save source files and clearly named exports.
- Check colors in real text, link, and button combinations.
- Collect authentic photos with permission to publish.
- Record image purpose and asset approval responsibility.
Written with AI-assisted research and drafting, with source checks and editorial review for this guidebook. Platform facts link to official documentation. Examples and recommendations are our own; no client results are implied. Sources reviewed October 8, 2026. About Getting Found Local