Skin Reorganization - Let's share some ideas

compibot

Verified User
Joined
Aug 21, 2005
Messages
690
Location
Spain
Skin Reorganization - Domain list by default

Hello folks.

I have now been using directadmin for over 2 years, and I wanted to point something out that has created a good 5% of my ticket matters.

When a new user purchases a hosting plan, and logs in for the first time, it's all good. But as soon as he registers a new domain and logs back in, as all of us managers now, we get a ticket in the box asking "Where/How do I add my newly registered domain"?

Well, I've been thinking of a better aproach. And want to get some of everyone's juices flowing to make the panel a bit more intuitive.

My idea is to automatically show the list of domains , even if there is only one domain, and on top of that, have a link to add new domains right on that same page. This will make the new customer learn, right away, two things, which will avoid 2 tickets being created:

1- He has to select which domain he goes into to see it's panel

2- He will learn that you can add more domains right there, where it makes sense to add more domains.

We could also take advantage of the Set Domain as Default domain right there on that page also and since there will be a lot of white space on that page (since there usually is anyways) we could show the domain quotas and such. Kinda like a quick glance of my domains deal.

Now what would be logical in this setup is that if you are on that page, the domains list page, and the client clicks on File Manager, he would start of at his root directory (the one in which they know they can go to any domain from there) BUT when they click on a domain to login to that domains' panel, if they press File Manager, it takes them directly to that domains folder (So they only see the folders related to that domain) Then we can get rid of the public_html folder link at the root directory.

I think and am confident this setup would really make directadmin a lot more intuitive and logically structured for a new customer.

What do you think ?
 
Last edited:
I think the new x3 cpanel skin has some good attributes. Each feature when you click on it has a brief description of what the function or tool is and does. It also has a small video tutorial that you can click to watch. This is a great feature for novices.
 
we get a ticket in the box asking "Where/How do I add my newly registered domain"?

I explain that in the email they get after registering for service. I never get a ticket.

We could also take advantage of the Set Domain as Default domain

I have have never understood the idea of a default domain. They are all independent of each other. I am just as likely to upload to any of them.

Then we can get rid of the public_html folder link at the root directory

I already do that as that is very confusing to users who feel as I do there should not be a default domain.
 
toniramos,

I'm confused, because I run the enhanced skin for my clients, and unless they have only one domain they already see their list of domains when they log in.

While I agree we would eliminate the three or four support requests we get a year (that's all we get) from clients who can't figure out that they have to click on Domain Setup to install a new domain, I'm not sure it's worth it to have every client login require an extra click-through. Perhaps I'm wrong, but that's the way I see it.

Perhaps in addition to having Domain Setup we have a link on the main login screen to Add Domain; do you think that would be helpful (don't forget; many plans don't allow multiple domains)?

Jeff
 
Then we can get rid of the public_html folder link at the root directory
How about the majority of our clients, who have only one domain, and on other control panels are used to being able to go directly to public_html instead of having to change directories into domains/example.com before they can upload? To me having a link to public_html is valuable both to me and the average user.

What I'd like to see is having the link always go to the first domain added; never to a newly added domain, unless changed by the user; I think this would cause less confusion.

Jeff
 
jlasman, you can change the symlink by changing the default domain :) About the majority of our clients - my suggestion is just to make an option for that, but not "remove" this feature.
 
Sorry guys, I must have missed the responses on this topic.

unless they have only one domain they already see their list of domains when they log in.

Not correct. They first need to click Domains, and then they see the list of domains. But if the link to public_html is always there , they will always click it (until the either realize they just overwrote the wrong domain or send us a ticket asking "Where is my other domain? I click on public_html and it's not there")
While I agree we would eliminate the three or four support requests we get a year (that's all we get) from clients who can't figure out that they have to click on Domain Setup to install a new domain, I'm not sure it's worth it to have every client login require an extra click-through. Perhaps I'm wrong, but that's the way I see it.

I don't get TOO many tickets either, but this idea is part of the overall "reorg" I was thinking about.
Perhaps in addition to having Domain Setup we have a link on the main login screen to Add Domain; do you think that would be helpful (don't forget; many plans don't allow multiple domains)?

Yes, that's why I tossed out the idea. Again, this is part of the overall idea. This would be helpfull becuase as soon as they login , they see the most important object, the domain list. A good starting point for a multidomain control panel, don't you think ? Just like it would be a good start pointo for the client to get used to seeing the place where their domains would be listed in FTP, instead of figuring out how the public_html link works on trial and error.

The idea is this :

BAM: List of domains , if you only have one, no problem, click add another domains. This explains many things right off the bat, and leaves no room for "ummm,... how do I add another domain" or "oh,. that's how the public_html link works,.."

I like the current system, but I think it can be a lot more intuitive.
 
How about the majority of our clients, who have only one domain, and on other control panels are used to being able to go directly to public_html instead of having to change directories into domains/example.com before they can upload? To me having a link to public_html is valuable both to me and the average user.

Well, the majority of my clients are new to anything clients. But yes, I do see this as a problem for the majority of your clientes.

What I'd like to see is having the link always go to the first domain added; never to a newly added domain, unless changed by the user; I think this would cause less confusion.

Better than that: create a public_html link that is called public_html_domain.com for each newly added domain instead. What do you think ? :D
 
Not correct. They first need to click Domains, and then they see the list of domains. But if the link to public_html is always there , they will always click it (until the either realize they just overwrote the wrong domain or send us a ticket asking "Where is my other domain? I click on public_html and it's not there")
Are you writing about the File manager and FTP logins? I was referring to the Control Panel itself. Sorry for any misunderstanding.
as soon as they login , they see the most important object, the domain list.
Which is exactly what my users see, when they log into the Control Panel, before they even choose files.

Just what do you mean? An ftp login? That could be done by a simple change to either /etc/passwd or perhaps one of the proftpd configuration files.

But that would make it from impossible to hard for users to find other files they may need, which are above the domain directory tree.

Or do you mean some other login?
List of domains , if you only have one, no problem, click add another domains. This explains many things right off the bat, and leaves no room for "ummm,... how do I add another domain" or "oh,. that's how the public_html link works,.."Again, this is exactly what we see when we log in to the control panel. Where do you mean?

Thanks.

Jeff
 
I think we're not on the same page.

What I mean is this:

Scenario 1:

A new user logs in for the first time. Only has one domain obviously. So when he first logs in he will see the Full Blown control panel for that domain.

Uploads his files via FTP click on the kindly provided public_html link which takes him directly to the domain folder (therefor not learning the real structure of his account)

A few weeks later...

The same user needs to add a new domain. "Where the hell do i add a new domain ??". I'm sure we've all experienced this one too many times. He finally adds a new domain. Logs in via FTP (still with the default FTP account) and says to him self,.. umm,.. so where is my new domain ? This all looks the same. This where the problem begins. This is the uncertanty that creates tickets, or even worse, creates tickets becuase the client did not ask himself if the public_html link was for the old or new domain, and just overwrote everything from the new domain.

Scenario 2:

The same user logins in to his control panel, and sees two domains. "Oh great, this is easy, I just click on the domain I want to work on, and work on the full blown control panel for this domain". Everything here is fine and dandy right ?

Errrrrrrr. Incorrect.

A few minutes later...

The user clicks on the File Manager button. "Oh, oh.... Here's this public_html thing again.

And the uncertainty repeats itself.

So,... my idea would create this scenario:

Scenario 1:

A new user logs into his newly created account. Sees a link for his domain (and above a link to add a new domain). He says to himself, ok cool, this is the only domain I have , so I guess I have no other choice but to click it. And cool, I see an -add domain- button, so I guess that's where I add any new domains." He clicks on the only domain he has , and Tada !! Full Blown control panel for that domain.

A few minutes later...

"Ok, I want to upload an index.html file to overwrite the deafult one. Oh, I guess I do this in the File Manager" He clicks on file manger,. and he sees a list of folders. domains , imap, etc.. "Hmm,.. I think domains sounds about right. Oh,. there's my domain folder. Ok, there's the public_html folder they were talking about." He uploads his file,. and he's a happy camper. No uncertainties, pretty intuitive. No questions asked.

Scenario2:

The user need to add a domain. "Hmm I need to add a domain. Ohh yeah,.. right here,.. I remeber -add domain- " He adds his domain and TADA ! He now sees two domains. "Cool, this is easy. No I just go to file manager, click on domains, my domain folder, its public_html folder, just like I did with the previous"

No doubts, pretty intuitive, no confusion, no tickets, happy customer, happy tech support.

-----

Hopefully I got the idea across, and I understand you might not agree or have a better idea.

What do you think ?

:)
 
It makes quite a bit of sense for a multi-domain environment.

At the expense of a bit more complexity for the single-domain user.

Are most users single-domain users or multi-domain users?

I understand what you wrote. For the moment I'm neutral.

Jeff
 
Our main point of sale is that we offer a multidomain Control Panel.

Most of our users have more than one domain. And most single domain users are new clientes, and eventually will purchase at least one more.

This is what we push in the sales department. We actually give the first domain away for free, for ever, so most will get a second one soon or immediately.
 
Hello,

We actually used to have it like that, but it became redundtant for those Users who only had 1 domain name. They didn't need to see the only domain they had... so if they only have 1 domain, it sends them a location redirect to the "show domain" page. They actually *do* see the list page you're referring to right off the bat, but the redirect was added from there for when they only have 1 domain.

What I'd assume you'd want would be the abilty to shut off this redirect?

We won't make it a standard option as the majority of Users only have 1 domain anyway. Adding it as a directadmin.conf option is a possibility, let me know what you think.

John
 
Right on !!! If it's as easy as having an option to turn off the redirect in admin settings, that would solve that problem instantly.

The other pain I have is the public_html link, which is a similar problem. It's perfect for one domain users, but as soon as they add there 2nd domain, that's when questions start arising, so another switch to eliminate (or not place for new users) the public_html link in both the ftp and file manager would solve my other headache !

Thanks for your attentiveness :)
 
Back
Top