[FEAT] Content Drive: Create Assets

EPIC Title

Content Drive: Create Assets

Vision

Our users expect to be able to create assets in our digital asset repository, not just new content items, but also new folders, new files, new videos and new images. The image below shows the latest version of the "Add new" menu for content drive but the latest discussion calls for only folder, files, pages, content items.

Problem or opportunity

At the moment we don't treat objects like files, folders videos and images as first-class citizens, meaning we don't treat them as native objects like google drive would, instead we complicate these file types by assigning them different unexpected base types complicating matters. By simplifying the creation of these popular objects and treating them in a straight forward manner like the OS does or Google Drive does we will enable our users to quickly create new assets and manage them more effectively.

Solution

Support adding files, folders, images and content types in a straight forward manner.

Out-of-Scope

We are not supporting adding pages from content drive.

Market Validation & Competitive Positioning

Competitive analysis was done as is included in the kick off deck found in the parent Pillar for this Epic.

Personas

• Developer teams
• Content teams
• DevOps teams
• Sys Admin

Links As Appropriate

• See main Pillar description for links.
• Figma

Review the Content Drive requirements, the linked Figma design, and the parent Pillar referenced by the issue. Reconcile the conflicting scope around files, folders, images, pages, and content items before identifying implementation entry points. Done means the agreed asset types can be created from the Content Drive menu, with pages excluded if that remains the decision.