The default (only?) folder where sites are stored is Studio, which is generic and could be confusing

[haszari]

Quick summary

Minor feedback – not a major issue but I think care should be taken when claiming a subfolder of user's Documents.

• The folder where sites are stored is Studio.
• This could mean many things to many users. They could also have an existing folder named Studio.

Suggested fix

• Default to WordPress.com Studio. This is somewhat long but completely unambiguous. I think it's important to clearly associate this tool with Automattic/WordPress.com brand – a positive association! Could be confused with WordPress.org`.
• Add a user option to customise/change the folder name.

Steps to reproduce

• Start studio app.
• Make a site.
• Observe where the site's code is saved in Documents folder.

What you expected to happen

• Site code / documents to be in a folder that is clearly associated with WordPress.com, or some other clear unambiguous branding/tooling name.

What actually happened

• Sites are stored in ~/Documents/Studio, which is generic and feels like a "land grab".

Impact

All

Available workarounds?

There is no user impact

Platform

No response

Logs or notes

No response

[wojtekn]

Thanks for adding a feature request. I don't agree that defaulting to WordPress.com Studio would lead to a better user experience. Such a path is longer, and includes a space, so it could make running CLI commands and navigating through CLI less convenient.

A good approach to the problem would be to let users change the default path to a custom one, which we have tracked under #587. Such a feature would be useful for me personally, too, as I would be happy to keep Studio sites along with other sites in ~/Sites directory.