Two inaccuracies found in the "Content collections → Generated properties" section of packages/www/docs/template-data.md, verified against packages/nuekit/src/collections.js.
Bug 1: is_prod incorrectly listed as a collection item property
Line 150 lists is_prod under "Generated properties" for collection items. However, collections.js only spreads { ...meta, url, dir, slug } onto each item — is_prod is never added per item. It is a top-level template context variable, not a collection item property.
Fix: Remove the is_prod bullet from the collection "Generated properties" list, or move it to the broader template context section where it belongs.
Bug 2: match should be include
Line 155 reads: "Only files matching the match patterns are included"
The actual config key is include (correctly documented in configuration.md). There is no match key in the source.
Fix: Change `match` → `include` on that line.
Two inaccuracies found in the "Content collections → Generated properties" section of
packages/www/docs/template-data.md, verified againstpackages/nuekit/src/collections.js.Bug 1:
is_prodincorrectly listed as a collection item propertyLine 150 lists
is_produnder "Generated properties" for collection items. However,collections.jsonly spreads{ ...meta, url, dir, slug }onto each item —is_prodis never added per item. It is a top-level template context variable, not a collection item property.Fix: Remove the
is_prodbullet from the collection "Generated properties" list, or move it to the broader template context section where it belongs.Bug 2:
matchshould beincludeLine 155 reads: "Only files matching the
matchpatterns are included"The actual config key is
include(correctly documented inconfiguration.md). There is nomatchkey in the source.Fix: Change
`match`→`include`on that line.