Record the source and the decision to use it
For each important asset, identify whether it is original photography, licensed stock, customer-supplied material or generated content. Keep the relevant service and licence references and record who approved publication. Do not describe a generated scene as evidence of a real team, office or customer project. If the image makes a factual claim, choose evidence that can support it.
Make later reuse a separate check
An asset suitable for a website may raise different questions when used in a brochure, advert or another market. Review the actual terms and context rather than assuming unrestricted ownership. This guide is a record-keeping workflow, not a legal opinion about any generator’s output. Resolve uncertain rights or representations with appropriate advice before relying on the material.
A practical check before you buy
Pick one hero image and trace its source, approval and intended uses. Ask another editor whether the record is sufficient to replace, retire or evaluate reuse of the image without contacting the original designer.
| Decision | What to consider | What to check |
|---|---|---|
| Origin | How the asset was created | Keep a retrievable reference |
| Representation | What the image implies | Avoid fabricated real-world proof |
| Reuse | Actual terms and context | Review the intended new use |
An illustrative business scenario
A UK business can separate a conceptual technology illustration from photographs that are presented as its real staff or premises.
This is an illustrative scenario, not a claim about an ImbaHub client or a promised result.
Discuss the right scope with ImbaHub
ImbaHub builds fast static websites with Astro, with editing through Imba CMS and Imba Builder. Start with the customer task described in this guide and ask which content, integrations and ongoing responsibilities your project needs. Agree the scope before comparing the investment.