V0.44.0
Name:v0.44.0Status:planning

v0.44.0 — Hero, cta and testimonial compose

The first marketing runes become compositions over section, beside the plugin runes they will replace. Before they can, a composed rune has to put its universal attributes somewhere other than its empty root, and state its chrome defaults (SPEC-145 D31–D34, SPEC-160 D7, SPEC-161 D1).

Milestone burndown: 10 open work items remaining; peak 10, started Oct 260246810Oct 26Nov 4
Open work items Ideal burndown
Progress 7/7 work items

Relationships

Related 33
History 5
  1. 0ec343f
    Content editedby bjornolofandersson
  2. c527aa0
    Content editedby bjornolofandersson
  3. 3c2340b
    Content editedby bjornolofandersson
  4. a785d87
    Content editedby bjornolofandersson
  5. 07d27ce
    Created (planning)by bjornolofandersson

Work Items

Done 7
WORK-680 main
A staging site renders the docs with staged runes in place of plugin runes
A second site, staging, renders site/content with the project runes in site/staged-runes/ preferred over the plugin runes they replace (SPEC-181 D1). It uses only existing configuration: runes.dir and runes.prefer (__project__).
high simple
6/6 criteria
WORK-681 main
Stage hero, cta and testimonial on the staging site
The composed hero, cta and testimonial move out of the test fixtures into site/staged-runes/. This makes the review of WORK-665, WORK-666 and WORK-668 possible: the runes' reference pages, the homepage and every other page that uses them, rendered with the compositions on the staging site.
high simple
6/6 criteria
WORK-683 main
Document the staging convention and rollout, and test that conversions follow it
Every conversion of a plugin rune into a composition is staged until it goes live, and goes live on its own (SPEC-181 D5, D6). Writing that down is not enough to make it happen, so this item also adds a test that fails when a conversion skips staging.
medium simple
4/4 criteria
WORK-684 main
The plugin hero accepts start and end for align, and the site content uses them
The composed hero takes align="start | center | end", which is section's vocabulary. The plugin hero takes left | center | right. The staging site renders the same content as main, so align="left" on the homepage and on the hero reference page would be invalid there (SPEC-181 D7). The plugin hero learns the new values first, and the content moves to them.
high simple
5/5 criteria
WORK-685 main
The plugin testimonial accepts author and role attributes, and the codemod is applied to this repository
The composed testimonial (WORK-668) takes author and role attributes and reports a **Name** — Role paragraph as content-unmatched. The plugin testimonial takes no author attribute. So WORK-668 built refrakt marketing migrate-testimonial but did not apply it: the rewritten content would not have rendered through the plugin.The staging site renders the same content as main (SPEC-181 D7). The plugin testimonial therefore learns the attributes first, and the codemod is then applied.
high simple
6/6 criteria
WORK-686 main
A paragraph field takes an item model, and fills the rune's own attributes
The content model reads structured values out of a list item (itemModel) and a heading (headingExtract), but not out of a paragraph, and what it extracts can only reach an emitted child or $each (SPEC-182). This item adds both missing pieces, reusing the list-item vocabulary.
high moderate
7/7 criteria
WORK-687 main
testimonial reads its byline from the paragraph again, and the attribute migration is reversed
The staged testimonial reads **Name** — Role through WORK-686's paragraph item model, and keeps author and role as the alternative form (SPEC-182 D6). The content migration and the codemod that pointed the other way are reversed before v0.44.0 is released (D7).
high simple
7/7 criteria