Cookie policy: the page nobody reads and everybody checks
A cookie policy lists what you set, why, and how long it lasts. What has to be in it, why the banner is the real compliance question, and the common mistakes.
A digital catalog is usually built as a PDF because print habits carry over. That choice decides whether it is findable, updatable and measurable — or none of the three.
A digital catalog usually starts as the print catalogue exported to PDF. It looks right, it emails well, and it is easy — which is why most companies stop there and then wonder why nobody finds it, why the prices in circulation are eight months old, and why there is no way to tell which pages were read.
PDF and web are not the same product. Each is genuinely better at something, and the honest answer for most businesses is both, with one of them treated as the source.
Whichever you send, keep one source of truth. A catalogue maintained separately as a PDF and as web pages diverges within two updates, and then the price you quote depends on which file the customer opened.
In Ettex Sites, the web half of that is the builder itself: store and landing templates, 70+ sections, a live canvas, theme control over fonts, colours and spacing, SEO fields with an auto-generated sitemap, custom domains with certificates issued automatically, forms feeding a built-in leads inbox for catalogue enquiries, and built-in analytics showing visits, referrers and page stats — which is how you learn what people actually looked at. For the sendable copy, Ettex PDF fills, annotates, organises pages and exports flattened, print-ready files, and any PDF can be turned into a signature request when the catalogue becomes an order.
The catalogue draws on data that has other jobs. A product catalog is the operational version of the same records, and inventory management depends on the identifiers in it — which is why a marketing-only copy tends to drift from what is actually sellable.
Your product range in a form people can open on a screen — most often a PDF, a set of web pages, or both fed from the same product data.
Web for being found, updated and measured; PDF for a fixed, sendable, printable copy. Most businesses need both, generated from one source.
Small enough to email — under about 10 MB. Above that, share a link, because attachment limits vary and silent bounces are common.
Date the catalogue, state a validity period, and keep prices in one place that both versions are generated from. Never edit the PDF alone.
Only on the web version, page by page. PDFs give you a download count at best, which is why the web version is worth maintaining even when the PDF is what gets sent.
Treat the digital catalog as data first and documents second: one structured product list, a web version that can be found and measured, and a PDF for the moments when someone needs a copy to keep.
A cookie policy lists what you set, why, and how long it lasts. What has to be in it, why the banner is the real compliance question, and the common mistakes.
A modern slavery statement is public, annual and signed by the board. What has to be in it, where it goes, and the sentences that make it worse than saying nothing.
Most intranet projects fail on maintenance, not on features. Deciding who owns each page before launch matters more than which platform you pick.