4 ms·
I like the sub-domain approach. It's fast and nice enough. I'd focus on UI consistency; pages have different navigation elements. Issues trello-style board is c
by ErrantX 10y ago
I like the sub-domain approach. It's fast and nice enough. I'd focus on UI consistency; pages have different navigation elements. Issues trello-style board is cool but let down by over-simple styling.
FYI the default avatar image (https://errant.gitly.io/img/avatars/default.png https://errant.gitly.io/img/avatars/default.png) seems to be missing? On the issues page, JQuery UI seems to be missing too.
If you keep working on it I'll probably keep using it :)
- alex-m 10y agoYeah, I really wanted to have unique subdomains for each user. The design will be improved. This is a very, very early release. I'm also not a great designer, so hopefully I'll get some help there :) The entire issues section will see a huge update in 2 days.
- jazoom 10y agoWhat's the actual benefit of a subdomain for each user?
- chris_overseas 10y agoHopefully "user" really means "company" rather than individual user. Otherwise copy/pasting URLs between colleagues won't be much fun.
- jazoom 10y agoI'm sure it does. But I still can't see the benefit of a subdomain rather than a subdirectory.
- daenney 10y agoIt could be easier for load balancing or if you want to shard. You could do it at the DNS level at that point, without needing to strip the TLS bits, decode the HTTP request and go from there. For the end user though I can't see much of a benefit of a subdomain over a URL path, or the other way around. I don't think it matters much but the author might have bigger plans in which having the subdomain could be easier.
- crackcomm 10y agoI hope it will be still as simple as it is now.