fix: improve domains page UX and button placement consistency

[ali-issa]

Fixes #1248

Changes

• Made domain text white to match other clickable elements
• Enhanced text truncation and responsive layout
• Replaced Button components with semantic elements for static information (ports/protocols)
• Improved hover states for better interaction feedback

Before & After

Context

These changes address usability friction points observed with new users. The improvements align the domains page with common platform patterns and Dokploy's existing UI conventions.

Testing

• Tested across different screen sizes
• Verified text truncation with long domain names
• Confirmed hover states and click interactions
• Checked accessibility with semantic markup changes

Let me know if you'd like any adjustments!

[MuhammadM1998]

Is adding a fixed "Open" button beside the edit & delete button a good idea? This will save an additional click to the Deployments tab then clicking the link. Maybe make it use the first available domain by default

[ali-issa]

@MuhammadM1998 I think you meant the General tab instead of Deployments. I completely agree with you. It was going to be my next PR. I had the same idea you mentioned, but how would we define which link is the default link? Dokploy itself doesn't differentiate between containers, so it doesn't know which one should be default. Maybe we could add a default switch in the modal when creating a new domain? If there's only one domain, it would automatically become the default.

[MuhammadM1998]

I meant to add it in the top section that's always visible whatever the opened tab is. See the screenshot It should be inside the red square beside the other buttons

but how would we define which link is the default link? Dokploy itself doesn't differentiate between containers, so it doesn't know which one should be default. Maybe we could add a default switch in the modal when creating a new domain? If there's only one domain, it would automatically become the default.

You're right that's why I think it should open the first domain by default until "Default Domain" gets implemented then we can use that. I suggested using the first domain for now as it would be faster to merge this then we can implement Default Domain in another PR.

[ali-issa]

But what would happen if a user deletes the default domain and adds a different one instead? There would be unintentional side effects. Plus there would be no way to choose which one is the default one. This is a common use case when users want to add custom domains for different purposes (like one for the app and another for pgadmin).

[MuhammadM1998]

But what would happen if a user deletes the default domain and adds a different one instead? There would be unintentional side effects.

As it opens the first domain, this would work without problems and the newly added domain would open.

Plus there would be no way to choose which one is the default one. This is a common use case when users want to add custom domains for different purposes (like one for the app and another for pgadmin).

I think you're right, maybe it should be implemented in another PR where we can allow the user to select a default domain, then show that default domain as the button target