Plan a small catalogue before its first release
A small catalogue can be difficult to maintain when its first pages have no consistent purpose or information model. This guide works through an invented independent homewares shop preparing its initial range. The exercise concerns content, navigation and review responsibilities; it does not operate a shop or describe products available to purchase here. The output is a modest publishing plan that another person can follow when products are added, changed or withdrawn.
Define the range before defining the menu
List the product types the business genuinely intends to offer. Note the differences customers need to understand and the information the business can verify. A menu designed before that inventory can force the assortment into attractive labels that do not match the available range.
For the hypothetical shop, lamps, small tables and storage objects might be relevant groups. Whether they belong under a room category, a product category or a curated selection depends on the customer's task and the depth of the range. There is no benefit in building a complex hierarchy for a handful of products that can be explained more directly.
Record the inclusion rule for each initial group. The rule should help a colleague place a new product without inventing another category every time. Leave room to revise the model when the range changes, but do not replace a usable first structure with speculative complexity intended for a business the shop has not yet become.
Establish a minimum useful product record
Identify the facts needed to explain a product responsibly. In our homewares example, those may include dimensions, materials, care information and relevant delivery conditions. Confirm the source of each fact and the person responsible for correcting it. A polished page cannot compensate for specifications copied from an unverified draft.
Use comparable definitions across products. Agree whether a measurement represents the overall object or a particular component. Distinguish an observed colour in a photograph from the manufacturer's description where that difference matters. The purpose is not a large database schema; it is a dependable set of information the shop can maintain.
Mark missing information before publication. A team can decide whether a page is ready with a stated limitation or should wait for verification. Filling a gap with a plausible adjective creates a different problem: the page now appears complete while the underlying fact remains unknown.

Assign a distinct job to each page type
The homepage introduces the range and provides useful routes. A category organises a selection. A product page explains an individual item. A guide helps with a broader decision. Those jobs can support one another without each page repeating the same general introduction to the business.
Write a short purpose statement for every planned page. If two statements describe the same audience and task, inspect whether the pages need clearer differentiation or could be combined. A small shop benefits from a concise, useful publication more than from a large number of near-identical pages.
Plan the internal routes at the same time. A buying guide should lead to relevant categories or products where appropriate, and the product explanation can point back to a helpful guide. The relationship should be understandable in the surrounding text rather than appearing as an arbitrary link inserted into every paragraph.
Prepare images as information, not decoration
Create an image plan with a role for each view. A clear product image can show shape; a context image can suggest setting; a detail image can show a particular construction feature. Confirm usage rights and keep the original source information in the working record.
Do not let a styled photograph carry a specification it cannot establish. A lamp shown beside a chair does not necessarily communicate accurate scale. Provide dimensions as readable information and make any illustrative setting clear. The shopper should not have to infer important facts from a decorative composition.
Review the images at mobile size. Details can disappear when a photograph is reduced or cropped, and a caption may become separated from the image it explains. The publishing plan should include that check rather than treating image upload as the final step in visual review.
Give changing information an owner
Availability, delivery conditions and product details can change after release. Decide who updates each type of information and how a colleague reports an error. A simple ownership note can prevent a product page remaining misleading because the writer assumed the operations team would maintain it.
Include the related pages when a product changes. Withdrawing an item may affect a curated collection, a buying guide and a homepage feature. The product record should make those dependencies discoverable. Otherwise each update becomes a search through the whole website for mentions somebody remembers from the original launch.
Keep a record of substantial decisions. If a category is renamed, note why and review established links before changing its address. If a product has a genuinely relevant replacement, document the relationship. Do not let an automatic technical rule decide that any current product is an appropriate substitute for the unavailable one.
| Record | Information to preserve |
|---|---|
| Range definition | List the initial products and the differences a customer needs to understand. |
| Verified record | Identify the source and owner of dimensions, materials and changing conditions. |
| Page purpose | Give categories, products and guides distinct jobs with justified connections. |
| Release readiness | Check a complete route and assign the facts that need ongoing maintenance. |
Test a complete shopping-information route
Choose a representative task, such as finding a lamp suitable for a small desk. Begin at the homepage, follow the category and inspect a product. Check that the visitor can find the dimensions, understand the relevant conditions and return to alternatives without losing the thread of the decision.
Repeat the route without relying on knowledge of the internal catalogue. Link labels that seem obvious to the team may be ambiguous to a new customer. Record specific points of uncertainty and connect each to a proposed change. A finding about an unclear selection label is easier to resolve than a general request to make the site more intuitive.
Include unavailable and unfamiliar addresses. The website should communicate when a resource is missing rather than silently disguising the condition as a successful visit to an unrelated page. These responses form part of the customer journey even though they rarely appear in the launch presentation.
Release a structure the business can maintain
Prioritise a coherent initial range with verified information and working routes. Record which improvements remain for later and which are necessary before publication. That distinction helps a small team finish a useful release without pretending that all future catalogue needs have already been solved.
After release, review recurring customer questions alongside the available measurement. A missing specification or unclear delivery explanation may deserve attention before another promotional article. Keep observations separate from assumptions about commercial effect, especially when stock or pricing changes during the same period.
The first catalogue should leave the next editor with a practical system: page purposes, selection rules, product facts, image roles and named owners. Those foundations make later growth easier to understand and control. Adding products then becomes an extension of a maintained explanation rather than an accumulation of pages whose relationships nobody can reliably describe.
Return to the Collection & Context main edition for the wider explanation and its practical context. Continue with build a collection page with a clear selection rule when that related question becomes relevant.