Summary:
//Schedule and publish campaigns from the campaign list and the campaign builder.
Intent/Outcome:
Intent:
Build on MVE3 using F14 requirements to bring ideascale replacement to life for admins and test the flexibility of the system we’ve built.
Outcome:
Description / User story:
//…
UX Story:
Requirements
[ ] MVE3 + Fund14 requirements - Category Briefs - Ideascale: 1 example to bring guidance to life.
[ ] Make 1 brief category actionable.
[ ] Niels brings all Category parameters into One source of Data Truth sheet first.
[ ] Niels brings all Category parameters into the Campaign Builder Setup/Detail Categories section. (1 example)
[ ] JSON is the simplest approach we’ve identified that offers the flexibility and scalability we need, with minimal dev effort. Campaign / category templates defined through this initial ad hoc process will become re-usable templates to clone in future campaigns.
[ ] Segment/Section/Topic(s) is the core structure we use throughout the system as this provides a balance between cognitive load for proposers, and relation content in context.
Acceptance Criteria:
…
Additional information:
Who does/prepare the data architecture work? Nathan / Neil are responsible for designing databases and APIs, and data-structures which are also future facing (Decentralized/Distributed solutions) Lucio will be the one to define each JSON. Our work from the design side is to just give a data input to paste JSON.
Refinement discussion
Consider bringing all parameters in the OSDT? (One source of Data Truth - link) + MVE designation.
…
Original notes, questions & answers
OLD TICKET / BRING OVER:
Summary
Detail category brief
Description
Summary
Extend the basic category brief configuration & editing introduced in #1111 (MVE3) to meet the needs of Ideascale replacement in Fund14.
Description
An admin workflow to configure the category brief data structure via JSON pasted into a textbox, then edit specific values within that data structure through a user friendly UI. Basic page structure will be defined and implemented in previous MVE, and this MVE aims to validate those foundations against actual Fund14 requirements. Practically, this means bringing in additional data fields for editing, and identifying which fields must be editable by non-technical admin, so that we might streamline the editing experience.
User Value
As an admin, I need to have confidence that the Voices admin configuration capabilities meet or exceed what I have today in Ideascale, so that I can get off of Ideascale in Fund14. I also need to have a friendly UI for editing specific fields, so that I can empower non technical team members to make important changes.
UX Story
When I click "configure", I can enter a JSON in a text field. When I click "save" then the UI validates and renders the JSON.
When I click "detail", then I enter a new page that allows me edit the values of specific fields in the JSON. When I click "save", then my changes are saved, and I'm returned to the previous screen. I can also choose to exit without saving.
After configuring and detailing the category brief, I can enter preview mode to see how category details appear in the discovery space, workspace, and voting space.
Acceptance Criteria
[ ] Collect actual category brief details for Fund14
[ ] Create version of mockups that reflects actual category brief questions, and actual category brief details
[ ] Simplify mockup of UI to edit details to only include fields required to be editable by non technical admin
Estimate 2d
Summary: //Schedule and publish campaigns from the campaign list and the campaign builder.
Intent/Outcome: Intent: Build on MVE3 using F14 requirements to bring ideascale replacement to life for admins and test the flexibility of the system we’ve built.
Outcome:
Description / User story: //…
UX Story:
Requirements
Acceptance Criteria: …
Additional information:
Refinement discussion Consider bringing all parameters in the OSDT? (One source of Data Truth - link) + MVE designation. …
Original notes, questions & answers
OLD TICKET / BRING OVER:
Summary
Detail category brief
Description
Summary
Extend the basic category brief configuration & editing introduced in #1111 (MVE3) to meet the needs of Ideascale replacement in Fund14.
Description
An admin workflow to configure the category brief data structure via JSON pasted into a textbox, then edit specific values within that data structure through a user friendly UI. Basic page structure will be defined and implemented in previous MVE, and this MVE aims to validate those foundations against actual Fund14 requirements. Practically, this means bringing in additional data fields for editing, and identifying which fields must be editable by non-technical admin, so that we might streamline the editing experience.
User Value
As an admin, I need to have confidence that the Voices admin configuration capabilities meet or exceed what I have today in Ideascale, so that I can get off of Ideascale in Fund14. I also need to have a friendly UI for editing specific fields, so that I can empower non technical team members to make important changes.
UX Story
When I click "configure", I can enter a JSON in a text field. When I click "save" then the UI validates and renders the JSON.
When I click "detail", then I enter a new page that allows me edit the values of specific fields in the JSON. When I click "save", then my changes are saved, and I'm returned to the previous screen. I can also choose to exit without saving.
After configuring and detailing the category brief, I can enter preview mode to see how category details appear in the discovery space, workspace, and voting space.
Acceptance Criteria