landing-page-structure

Structure a landing page as one argument, not a stack of default sections.

The failure this fixes

Asked to build a landing page, a model drops in a reorderable stack of default sections - hero, feature grid, testimonials block, pricing, FAQ, footer - in template order, with no argument connecting them. The tells: proof exiled to a lone "What our customers say" section (or the footer) instead of sitting next to the claim it backs; a hero carrying three or four competing CTAs; a uniform icon-row feature grid; and a 9-11-field form because the fields were available, not needed. It passes visual inspection but has no story - you can shuffle the sections without hurting comprehension, which proves it is parts, not a sequence.

When to use / when NOT to use