Repository navigation
[EPIC] Content Drive: Upload #35436
Description
Overview
Folder-level upload preferences that control whether uploads create dotAssets ("Assets") or FileAssets ("Files"). The upload button label communicates the folder's effective type — no separate indicator needed. Includes drag-and-drop, MIME-type routing for Assets mode, preference inheritance, and duplicate file handling.
Problem
Content Drive is folder-and-file oriented, but uploads currently create dotAssets by default, which breaks the mental model for customers using FileAssets (~75% of existing customers). There is no compelling product reason to force one type over the other.
Design Principle
The UI never surfaces "dotAsset" or "FileAsset." Only "Assets" and "Files."
Folder States & Upload Behavior
| Folder state | Button label | Drag-and-drop | File creation |
|---|---|---|---|
| Explicit or inherited "Assets" | Upload Assets | Direct | Routed by MIME type |
| Explicit or inherited "Files" | Upload Files | Direct | All created as FileAssets |
| No preference (default) | Upload | Triggers choice dialog | Depends on user choice |
No preference state: Drag-and-drop triggers a choice dialog. If user has edit permission, a "Remember my preference" checkbox is shown.
Preference Inheritance
Child folders inherit parent's preference unless explicitly overridden. Inherited folders behave identically to explicitly set folders.
Duplicate File Handling
Replace, Keep both (appends suffix), or Cancel — following macOS / Google Drive pattern.
Out of Scope (v1)
- Site-level or user-level upload preferences
- Predictable URL support for dotAssets
- Deprecating FileAssets
Activity
feat(content-drive): prompt Asset vs File on upload (dotCMS#35575) (d…
[-]Content Drive: Upload (EPICID-194)[/-][+][EPIC] Content Drive: Upload[/+]