How we write
Product pages are grounded in the application’s implemented contracts: Food inventory, recipe fit, Meals scheduling, Groceries, guided cooking, audit history, and safe Undo. If a workflow is not available, the public copy should not imply that it is.
Editorial guides separate observation from advice. A reader should be able to see the problem, the decision criteria, and the recommended routine without accepting a vague claim such as “best” on trust.
How comparisons are checked
Competitor features are checked against first-party product pages, support documentation, or official app listings. We record the review date, link the sources, avoid copying vendor language, and do not turn missing information into a negative claim.
Good Rotation is included when it fits the comparison. That relationship is disclosed plainly; rankings do not use affiliate payments, invented test scores, or review counts.
How updates work
The visible updated date and structured dateModified value change when the substance of a page is re-checked or improved—not for punctuation-only edits. Product comparisons should be reviewed again when a cited feature or platform changes.
Corrections should replace the inaccurate claim, update the date, and preserve a source that lets readers verify the new wording.
Food and safety boundary
These pages cover organization, planning, and product selection. They do not diagnose allergies, determine whether food is microbiologically safe from appearance, or replace authoritative temperature and handling guidance.