Inline editing for promo blocks

[kevwalsh]

Background

User Story or Problem Statement

As a user adding a reusable alert or a promo block, or editing a promo block, the editing experience is separate from the page i am trying to edit. I'd like to edit it (or create it) "inline".

Affected users and stakeholders

• Mostly, the editors of public websites who use embedded alerts often

Hypothesis

We believe that inline block editing will make it easier for CMS users to accomplish their tasks. We'll know this to be true when usability tests for editing a page with alerts or promos get good feedback.

Assumptions

• Tk
• Tk

(How will these assumptions be validated?)

Acceptance Criteria

• On node/67/edit, the alert field "Include alert" and the promo field in the Right Rail box provide a similar editing experience as adding a banner alert to a VAMC system operating status page, where you can either add an existing alert, using an autocomplete (or dialog box?) OR add a new one, using an inline form.

Runbook

This is particularly relevant for feature launches, or for making changes to the content model that require front end changes as well.

1. Step_to_get_to_production_X
2. Step_to_get_to_production_Y
3. Step_to_get_to_production_Z

Possible tickets to create for this epic

• Spike task, with some of the following attributes:

• Identify the baseline against which we will measure improvements
• Ideation (sketching, cross-displinary meeting of minds around how the problem may be solved)
• Analysis of the drupal landscape
• Possible implementation(s)
• Proof of concept or prototype
• UX writing discovery

• User research
• Design
• UX writing
• Usability testing (eg with a prototype or other design stimula)
• Implementation
• Documentation (What needs changing or adding to the documentation?
• Product release notes (How will we describe this feature to CMS users?)
• Training (Will any users require additional training?)
• Metrics (How will we measure any improvements)

Labels for this issue

• [/] Issue type (red) (defaults to Epic)
• CMS subsystem (green)
• CMS practice area (blue)
• CMS objective (orange)
• CMS-supported product (black)