@plitzi/sdk-server 0.38.2 → 0.38.4

package/skills/plitzi-authoring/reference/testing.md

@@ -13,8 +13,11 @@ expect((await inspectPage(page, handles)).problems).toEqual([]);
 It checks the open page and returns EVERY problem at once, one sentence each, naming the element and the reason:
 
 - every element the page owes is present and visible — its own and those of the layouts around it
-  (`heading "hero-title" is on the page but not visible: display:none on "hero"`);
-- every image arrived — an image element that failed says so (`data-plitzi-failed`), though its fallback loads;
+  (`heading "hero-title" is on the page but not visible: display:none on "hero"`). One a breakpoint hides at this
+  width (`mobile: { display: 'none' }`, or shown only at another width) is laid out by width, not missing: listed in
+  `hiddenAtWidth`, and checked at the width it shows at — run the check at each width you author for;
+- every image arrived — an image element that failed says so (`data-plitzi-failed`), though its fallback loads. A lazy
+  image out of sight (below the fold, or beside the screen in a carousel's track) has not been asked for yet, and waits;
 - nothing scrolls sideways (`the page scrolls sideways by 37px — widest: "cards"`);
 - no text is drawn in the colour painted behind it.
 
@@ -33,10 +36,12 @@ the list `inspectPage` holds a page to.
 
 Three flags say what a bare visit cannot promise, and `onScreen` leaves out:
 
-- `conditional` — on screen only under a condition of its own or of an ancestor;
+- `conditional` — on screen only under a condition of its own or of an ancestor, or with every child conditional (a
+  list of flyouts at rest);
 - `repeated` — inside a list row, so rendered once per row: several copies, or none while the list is empty. Address
   one with `.first()` / `.nth(i)`, in a test that knows the data;
-- `boxless` — a provider with no tag, which renders its children and no element of its own.
+- `boxless` — a provider with no tag, which renders its children and no element of its own; or a plugin whose
+  declaration says `drawsNothing: true` — behaviour rather than content, a clock that fires a flow.
 
 A `formControl`'s id names its wrapper: type into `locate('email').locator('input')`.
 
@@ -82,7 +87,7 @@ One code on one element; it comes back in `warnings` with the reason, and an ent
 
 ## What to check
 
-- **Every viewport and both themes.** Desktop, tablet (48–64rem) and mobile (below 48rem); `colorScheme: 'dark'` as well
+- **Every viewport and both themes.** Desktop, tablet (48–64rem) and mobile (up to 48rem); `colorScheme: 'dark'` as well
   as light.
 - **No horizontal scroll on a phone.** A column child grows to its content unless its parent stretches it; a code
   block or a wide table is what finds out.

package/skills/plitzi-authoring/reference/typed-sources.md

@@ -9,7 +9,7 @@ const site = source('site', home);
 apiContainer({ id: site.id, query: '/data/home.json', children: [
   heading({ from: site.data.hero.title }),
   text({ content: twig`{{ ${site.data.products}|length }} products` }),
-  list({ id: 'products', items: site.data.products, row: p => text({ from: p.item.title }) })
+  list({ id: 'products', items: site.data.products, row: p => listItem({ children: [text({ from: p.item.title })] }) })
 ] })
 ```
 

package/skills/plitzi-authoring/reference/validation.md

@@ -47,8 +47,9 @@ bar.
 
 2. **Fix, re-run, until it prints zero warnings.** What has one fix (`author` says how many) is written for you: `npx
    plitzi fix` shows it as a diff of your source, `--write` writes it and keeps it only if the space authors with each
-   fix gone and nothing new — a fix it cannot place, or that would add a problem, is said with the reason. Then
-   typecheck the project.
+   fix gone and nothing new — a fix it cannot place, or that would add a problem, is said with the reason. A
+   suggestion with one reading is written the same way (`content-attribute`: words and an icon held as children become
+   the button's or link's own `content` and `icon`). Then typecheck the project.
 3. **Look at it** — in a browser, at desktop and phone width, in both themes (see [testing](testing.md)). Stage 3 is
    thorough about MEANING and blind to what follows.