Streamline UI/UX and simplify a few things

PradeepC

Hello Team,

We have now implemented Enhance for our customers and have written some knowledge base articles to help them get used to the new control panel. But here are a few quirks we have heard from users and believe that other hosting companies might have heard the same.

Add Website Button: As we sell shared hosting to customers, who were previously on cPanel/Plesk we allow them one primary domain "website as enhance calls it" and unlimited addon domains to it. When a user wants to create a new website, he clicks on add website and doesn't understand why the staging domain is getting attached to it. We have to then tell them that they have to go and "Add Domain" to add a website. This has created a lot of confusion and explaining each and every client becomes time consuming.
Solution: Remove the "Add Website" button once the primary domain is attached to "account/website", so it won't create any confusion.
WordPress install outside subdirectory: Currently clients are only able to install WordPress in public_html directory and not outside it. Also "addon domains" are not correctly recognized by the Apps system.
Solution: Please enable this option and let us select the "addon domain" while installing WP.
Staging: I know that staging is coming a lot later, but please build it as such, that when a user wants to push the staging to live, he can do it on addon domains as well. This is a must, otherwise there won't be much use of the staging feature.
Document Root Not Created After Adding Domain: When a user creates the document root, a folder should be automatically created at the place where the user has selected.

These are the four main concerns currently being faced by us.

If anyone would like to add anything here, please add it.

Isaia-Arknet_PTY_LTD

The above are good points, but I would like to add some info to it.

All domains (including the primary domain) should be subfolders under public_html

Example
maindomain.com root folder /public_html/maindomain_com/
seconddomain.com root folder /public_html/seconddomain_com/
etc
subdomain.maindomain.com should be subfolders of /public_html/maindomain_com/
etc

The reason for this is we need to be able to count storage (total usage) _public_html + email + db
If domains are spread all over / then, it is probably a bit harder to count them.

Another option is to remove public_html altogether and create each domain as a subfolder of / including the main domain.

The above are only suggestions.

Rich

Isaia-Arknet_PTY_LTD I don't think it should be under public_html that's a SUPHP nightmare, speration is needed. Under root of the primary domain like other CP's do it would be fine.

Alias or subdomain as subdomain = / of primary domain user. Else subdomians setup as domains should have seperate userspace. I actually prefer setting up some subdomains as seperate domains for the extra seperation.

I really would like to see it like this so that docker sites can be offered and hold their volumes within the site folders for easy backup. Which can be outside of public_html. Since they usualy proxy as an external app.

Anything under public_html is subject to leakage with incorrect .htaccess