How it works
Packaging Weekly summarises other people’s reporting. That only works if it is done in a way the people doing the reporting would recognise as fair, so here is exactly what happens.
- 01
Publishers’ own feeds, and nothing else
Every Friday a scheduled job reads 31 RSS feeds across 5 regions. A feed is the publisher’s own offer of the content. Article pages are never fetched or scraped — that distinction is the legal position this publication rests on, not a preference.
- 02
Summarised here, in our own words
Headlines and summaries are written fresh from the extract the publisher put in the feed. Automated checks reject anything that keeps a run of the source’s wording, and anything failing twice is dropped rather than published. A short edition is the intended failure mode.
- 03
Balanced by region, capped per region
The busiest feeds are in the UK and Europe, so items are selected region by region and each region is capped, rather than the loudest publishers filling the page. A region with a genuinely quiet week is left out — no empty heading, no padding.
- 04
A person reads it before you do
The job opens a pull request, never a publication. A draft is reviewed against the linked originals and merged by hand. Nothing reaches this site without that merge.
The sources
31 feeds, grouped by region. The list lives in
data/feeds.yml in the open, and the weekly volume each
region produces is honestly uneven — Africa is essentially South
African, and outside India and Singapore most Asian packaging trade
press does not publish in English.
Suggesting a source
A source qualifies if it is English-language, packaging-specific, and the publisher’s own feed. Corporate blogs, supplier newsletters and SEO content farms do not, however much packaging vocabulary they contain.
If you publish one of the feeds we read and would rather we did not, say so and the source is removed the same day. No discussion needed.
Advertising and privacy
Ads are sold and served by us. There is no ad network, no third-party script, no tracking pixel and no third-party cookie — an advertiser gets markup or a static image, and nothing inside an ad makes a request anywhere else.