Methodology
WeekdayMealPrep.org is built around a discipline that many food sites avoid: the planning state should stay coherent across the whole product family. The builder should not be decorative, the week page should not be a disconnected demo, the prep schedule should not invent a new reality, and the grocery list should not pretend to be derived from a plan it never actually saw. This methodology page explains the product logic behind that approach.
1. Constraint-first planning
The site starts with constraints because real weekday systems break under unrealistic assumptions. Time, repetition tolerance, prep energy, and household complexity are treated as serious inputs rather than as decorative questionnaire theatre. That creates a more honest week shape before any shopping or prep narrative begins.
2. Continuity over novelty
The methodology favours continuity over superficial novelty. A user benefits more from one plan that stays connected through multiple pages than from several isolated outputs that each look momentarily clever. This is why the site treats the week as a backbone rather than a temporary display.
3. Explanatory density as product quality
A planning tool that only outputs boxes and buttons may pass a technical test while still failing a human review test. For that reason, explanatory copy is part of the product, not an afterthought. The site aims to tell users what they are seeing, how to interpret it, and where their judgment still matters.
4. Review standard
The site is reviewed across product pages, support pages, and trust pages as a family. A product page that works but feels skeletal is a quality issue. A legal page that exists but is too thin to establish trust is also a quality issue. A mobile navigation that technically opens but looks broken is not accepted as “good enough.”
5. Organisational, not clinical
The methodology is organisational. It can help reduce weekday friction, expose prep burden, and group shopping more practically. It cannot assess medical suitability, personal appetite, family dynamics, or food-safety execution. Those limits are not bugs in the legal pages; they are part of the honest design stance of the product.
6. Why policy pages are part of methodology
Trust language belongs inside product methodology because a planning tool becomes misleading the moment it sounds more certain than it really is. Privacy, terms, cookies, disclaimer, author identity, and contact are therefore treated as part of the site’s operating method, not just legal wallpaper.
7. Maintenance as part of method
A planning method is only trustworthy if it survives revision. When navigation breaks, when the trust layer drifts, or when a page starts feeling shell-like, the site treats repair as part of the method itself rather than as post-launch embarrassment.