Planning a Blog Post Template for Explaining Website Photography and Image Sourcing
Why a Repeatable Template Matters
Photography decisions slow down more blog posts than almost any other content task. Writers stall while hunting for the perfect image, designers receive files that are the wrong size, and legal questions about usage rights surface at the worst possible moment. A fixed template removes that friction.
This template is written for design-logix.co.uk readers who publish regularly and want a consistent process. Each section below maps to one stage of planning, so you can work through it before writing a single paragraph of the post itself.
Stock Versus Custom Photography
The first decision is whether the image should be licensed from a stock library or commissioned as custom photography. Stock is faster, cheaper, and often perfectly adequate for conceptual topics. Custom work is better when the subject is your team, your premises, or a product that no library can represent accurately.
- Stock works well for abstract ideas, backgrounds, and seasonal imagery.
- Custom photography builds trust when people or places are central to the story.
- Hybrid approaches mix stock for supporting visuals with custom shots for hero images.
Ask one question before choosing: could a competitor publish the same image without it looking wrong? If the answer is yes, stock is probably fine.
Licensing and Usage Rights
Licensing is where most publishing mistakes happen. A royalty-free licence is not the same as owning the image, and the terms can restrict print runs, advertising use, or resale. Always record the licence type, the source, and the date of download in your content calendar.
"Royalty-free means you pay once, not that you can use the image however you like."
For commissioned photography, agree in writing who owns the copyright and how long your usage rights last. If a contract is silent on this point, assume the photographer retains ownership and you hold only a limited licence.
File Preparation Checklist
Poor file preparation undermines good photography. Oversized originals slow page loads, while heavily compressed files look soft on modern screens. Prepare two versions of each image: a full-size master for the archive and a web-optimised export for the post.
- Resize the longest edge to the maximum width your layout supports.
- Export in WebP with a JPEG fallback for older browsers.
- Strip unnecessary metadata to reduce file size.
- Write descriptive alt text that reflects the image content.
Name files with lowercase words separated by hyphens, and keep the original untouched. Version control saves hours when a client asks for a different crop six months later.
Quick Reference Table
Use the table below as a summary you can paste into your own planning document. It keeps the key distinctions visible while you draft.
| Factor | Stock Photography | Custom Photography |
|---|---|---|
| Cost | Low per image | Higher, project based |
| Speed | Immediate download | Requires scheduling |
| Uniqueness | Shared with other sites | Exclusive to your brand |
| Licensing | Standard royalty-free terms | Negotiated contract |
Review the table whenever a new contributor joins the blog, and update the licensing column if your suppliers change their terms.
Publishing and Post-Launch Checks
Before publishing, confirm that every image has a source note, a licence record, and a prepared export. After publishing, test the page on a slow connection and a small screen to catch layout problems early.
Finally, schedule a quarterly audit of older posts. Licences expire, links break, and brand guidelines shift. A short review keeps your archive accurate and protects you from avoidable legal risk.
