Configure the destination path for image uploads from the Static Site Editor
Problem to solve
When a user uploads an image from the Static Site Editor, we need to know where to put it. This path can be different from project to project. However, users should not be expected to provide a destination during the image upload process. At the very least, this is an annoyingly repetitive task. But we also have to assume that some users will not know where the preferred asset directory is in relation to the page being edited. This could become a barrier to contribution or result in assets being stored in unexpected locations within a project.
Intended users
User experience goal
A user should be able to configure the destination directory for all images uploaded from the Static Site Editor.
Proposal
We should include a configuration option for the image directory used by the Static Site Editor. This configuration should be optional with a sensible default (like /images).
Further details
We want to limit the amount of configuration necessary to get the Static Site Editor up and running but having this configuration makes it so we don't have to prompt a user to provide a destination during the image upload process.
What does success look like, and how can we measure that?
Acceptance criteria
- User should be able to configure the location of images uploaded from the Static Site Editor