🎨 [Design] : Start Proposal opens New Proposal Modal

[nielskijf]

Estimate 4h

Summary: A really simple modal that allows the user to quickly start a draft proposal, no requirements.

Intent/Outcome: Intent: The top navigation always gives access point to the main cta based on the campaign stage, this needs some configuration in the Campaign builder. << The dynamics CTA in campaign builder can be pushed to another MVE, as that linked to Setup Roles.

Outcome: A one click access point to the most important action for the space / product segment you arae in.

Description / User story: As an Actor I want to see a primary call to action across all spaces I registered too, so I can quickly jump into action when I want too.

UX Story: //

Requirements

• [ ] Proposer sees Write Draft Proposal CTA in the top navigation without Category from spaces where applicable - Detail ! (Starts Proposal Modal)
• [ ] Write Proposal, modal, really easy. - recycle work done for MVE3

Acceptance Criteria:

• [ ] If fields are empty, prepopulate title with ‘Draft proposal title’ and description with ‘Write a concise description here.’

Additional information:

Refinement discussion Descope 1161, Focus on 1008, TICKET NEEDS ATTITION. Later: Proposer starts with Proposal Wizard (Start Proposal Modal + Choose your actions - visual list of actions - remind me? - Prepulate actions in the workspace/actiobar based on choices ) - OoS

Original notes, questions & answers

---

OLD TICKET, MOVE TO NEW USE CASE TICKET. Take 1008, descope 1161, It’s another ticket/use case. Don’t change expectation in CTA’s. Turning lurkers into participants needs a story driven approach, not a reroute in a cta. DP: Ask, don’t tell!

Summary

Streamline initial proposal creation via a modal that appears when users click 'Write Proposal' CTA buttons in various product segments (e.g. the Discovery space).

Description

A proposal creation modal that any user can access in whatever product segments feature the triggering 'Write Proposal' button CTA, and appears over other content currently on-page. The text input fields in the modal are purposely limited (proposal title - required, proposal description - optional) which allows users to quickly enter information without the need to complete a full proposal draft. Additional parameters for the new proposal can optionally be set at this stage. Controls at the bottom of the modal allow users to save the information entered as a proposal draft or open the full workspace proposal editor.

User Value

As a proposer I want a convenient way to get quickly get started writing a new proposal from wherever I am in the product so I can capture new ideas quickly and keep the majority of my focus on the proposal content not administrative actions.

UX Story

When I click a 'Write Proposal' button the new proposal modal appears. I can immediately start entering a title and description in the text field of the modal.

If I click the 'Options' button at the bottom of the modal, additional controls appear below the input fields, that allow me to optionally set parameters for my new proposal (inc. individual/team authorship, private/public visibility).

If I want to continue writing the full proposal I click one of the buttons at the bottom of the modal to open the draft proposal in the Workspace. If I am done writing for now, I click the other button at the bottom of the modal to save the entered information as a draft and dismiss the modal.

If at any point, I have entered any information in the modal, and I click its close affordance in the header or outside of it, a warning dialog appears asking me if I wish to save or delete the entered information.

Acceptance Criteria

Must

Include affordances for the (potential) configuration of:

• [x] Authorship (Individual, Team)
• [x] Visibility (Private, Public)
• [x] Status (Draft)

Allow input of:

• [x] Proposal title (text field; required; 60 characters max.)
• [x] Proposal description (text field; optional; 140 characters max.)

Trigger actions:

• [x] Save proposal as draft & close modal ('Save draft' button)
• [x] Open the entered information in the Workspace as a new draft ('Open in Workspace' button)
• [x] Toggle display of configurable options (described above)

Should not

• Actually allow configuration of the above options (other than proposal name, description) for MVE3

---

Initial ticket draft

> Create a Start Proposal Wizard that creates the Actor(s) preferences in a data-structure. > Title: Start proposal > Options (greyed out for now) > - Setup Organisation (tag) > - Set draft > - Select private / public at initial setup > > Participate as > - Individual (tag | data-structure) | Team (tag | data-structure) / Nathan > Select Category > > Based on selection / add Actions / Nathan > Detail Individual > Setup/Detail Team > > - grey out cat. select, team, private, target fund.) - See team modals

[b-farrington]

I've refined the ticket description to indicate user value, account for the proposal data model and outline interface requirements.

[b-farrington]

I've detailed the New Proposal Modal component as per the above requirements in UI kit here. Detailed functionality inc. basic menu and close warning dialog in Action Labels design file. Have also detailed a basic user flow.

Ready for review. Will incorporate into the overall MVE3 design files.