🎨 [Design] : Admin campaign publishing workflow

[mike-mcnulty]

@mike-mcnulty I did a minimal implementation of a Campaign Management Modal - Accessed through the top navigation. Top navigation also shows Draft / Published chip.

See Figma

Summary

Schedule and publish campaign

Description

As an admin user, I need to be able to publish campaigns, so that my community can participate in them. I want to be able to schedule them, so that I can set and forget campaigns once they are finalized.

AC

• User can save a campaign as a draft viewable only by other brand admins
• Users can configure / edit everything on draft campaigns
• Users can only edit copy on specific fields on live campaigns
• User can publish a finalized campaign for viewing by end users across spaces
• User can schedule auto-publish at a specific datetime in the future
  • User can toggle between local timezone and UTC when scheduling campaign

Out of scope (post MVP)

• Admin team consensus workflow before publishing

Open Questions:

• Does anything with campaign definition need to be posted to chain (along with proposals, votes rollup)
• Will admin API keys be signing anything? If so, should we introduce unlock password for admin role?
• Does admin need ability to retract / reschedule a published campaign?
• Discuss auto-create template for future use at point of publishing
• do we need ability to retract / de-publish an active fund?
• once in published state, which fields should be editable vs should be locked for editing?
• each completed fund auto saved as a new event / category template?
• metadata needed from admin view ie last updated, version history (auditing needs)?
• confirm: only need to see current, upcoming, and draft events in main menu; all historical events saved on archive / detail page

[mike-mcnulty]

@nielskijf @b-farrington anything outstanding here or design ticket can be closed?