Engineering 🧰 The Future II.i.

[Ismael-KG]

Title

The Future II.i)

Elevator Pitch

There are a series of questions that have cropped up and need a professional...

Tasks

The below, I think, should be done in order.

• [x] #46 -- This is first because it asks whether the latest yaml is apt and establishes the logic behind wip: true, all of which is needed to start migrating legacy stories and stories-in-progress
• [x] #101 -- This PR can go next, as it tests the new yaml, acknowledges the Yehudis contributions (😄), and does so on a story that is already published. It also possibly raises questions about how netlify shows previews of deployments...
• [x] #102 -- This is the first PR for the migration of a story-in-progress. If this works, I can continue copying and pasting to migrate legacy and wip stories!
• [x] #98 -- The Final Frontier, sort of... It's the end of the beginning. The start of the tunnel. The light at the end of the tunnel as seen through a rear-view mirror in the future.
• [ ] #107 , as per #31
• [ ] Issues in the ordinary sense as per this comment and [this other comment]().

Skills

Skill	Rationale
GitHub	Requires knowledge about PRs
yaml and markdown	I think these are the languages @yochannah has been using 😅
Netlify	There is currently a problem whereby previews of deployments in PRs lead to an error-404 page
Documenting	Key skill for Protocol 9!

[yochannah]

so for #46 I think it might be ready to go, and then you'll need to pull in stuff from the main branch for the next couple of PRs. It might be the UI can do that but I'm tired and can't remember right now. nudge me if needed, it'll take only 30 seconds.

[Ismael-KG]

I'll revise these in the morrow from my laptop — I am excitedly merging stuff from my iPad without checking what any of it looks like 😁

[Ismael-KG]

The image is squashy. How do we maintain the height-width ratio with the max-48px width, @yochannah?

[Ismael-KG]

So @yochannah was on absolute fire today and I am very very grateful! It's now time to face some growing pains. What I have found with a wip: yes story is that the text knows no boundaries!

I haven't tested 'wip: review` yet, and the trinary approach might bring up new problems yet! In the meantime, @yochannah, do you know:

1. How to keep the text from spilling out of the yaml box? And
2. How to add a media-status toggle? Relevant images can be hard to come by, and stories might go without an image for a while. If there was a media-status:view/hide toggle, the source and caption elements (where images are linked to and described) can be ignored when 'media-status: hide`.

What do you think? Tell me if anything needs clarifying!