Feature.

Full dark background. Top chapter header + 6-card feature grid (3×2).

Left side section label + title + checklist / Right side large screenshot or image area.

Left 2×2 feature card grid. Right device (laptop/tablet) mockup area.

4-card feature grid. Icon + title + description.

Left large image/mockup + right 3 features vertically stacked.

Left 4 feature cards stacked vertically. Right highlighted hero card (dark background contrast).

3 module cards grid. Each card has icon + title + description + tag chip. Product component introduction.

Left title/description + process flow card. Right 2×2 feature/mode grid cards.

Left side feature description + 3 benefit bullets. Right side terminal-style code panel (monospace, 3-4 line integration example). Common pattern in developer tool/API product pitch decks.

Integration slide listing 8 partner/external tool logos in a 4x2 grid, closing with an API integration request CTA.

A card-free two-column ledger that pairs each feature with the benefit it produces on the same row, using only row rules and a column divider so the one-to-one mapping carries up to five rows.

A slide that digs into one feature and nothing else. The feature name stands at hero size with a one-line definition beneath it, then the lower half splits asymmetrically: three numbered rows on the left carry the sub-capabilities that hold the feature up, and a single number on the right proves it. Unlike the other feature layouts, which list features, it makes exactly one argument per screen and stands on typographic hierarchy alone, with no screenshot or image asset.

A product spec sheet built for fact-checking rather than persuasion. Twelve label-and-value pairs across three groups of four rows, laid out with rules alone and no cards. Values are set larger than their labels because the value is the unit of reading. No icons, so adding items never adds meaningless ornament.

A product slide organized by the people who use it rather than by its features: four user types stand as vertical columns, each stacking account share, role, job to be done, features used, and the outcome gained, one line apiece. No cards and no faces are used, hierarchy comes only from the vertical rules between columns and the difference in type size, and a single accent rule plus an accent share figure lifts the primary type so the core user reads first.

A change ledger that lists what one release changed, one line per change with a New, Improved or Fixed chip. The left 34% holds an oversized version number, the ship date, a release summary and two headline figures; the right 66% stacks five changes on ruled rows as type chip, change name, the difference the user feels, and the product area. The version number is the largest type, so when and what changed reads first.