Clunky User Experience (UX) to move between multiple different websites for the block explorers and to Mine/Stack.
Good solution would be to aggregate the hosting of these sites:
https://miamining.com/https://mining.nyc/https://minecitycoins.com/
This is optimal in my opinion, I think having subdomains to differentiate the type of website being accessed is great for the UX: https://docs.citycoins.co/
All sites could be hosted under the domain of 'XxXxX.citycoins.com'
For example, 'docs.citycoins.com' , 'nycmining.citycoins.com'
Alternatives would be good to aggregate hosting of "like" sites. For example, miamining.com and mining.nyc could be co-hosted under the domain explorecitycoins.com or with subdomains like the examples above.
Another alternative would be to standardize the naming of these sites. miamining.com and mining.nyc are different, which can cause confusion. Standardization of 'CityIDmining.com' or 'mining.CityID', not both.
Additional context
Add any other context or screenshots about the feature request here.
Clunky User Experience (UX) to move between multiple different websites for the block explorers and to Mine/Stack.
Good solution would be to aggregate the hosting of these sites:
https://miamining.com/
https://mining.nyc/
https://minecitycoins.com/
This is optimal in my opinion, I think having subdomains to differentiate the type of website being accessed is great for the UX:
https://docs.citycoins.co/
All sites could be hosted under the domain of 'XxXxX.citycoins.com' For example, 'docs.citycoins.com' , 'nycmining.citycoins.com'
Alternatives would be good to aggregate hosting of "like" sites. For example,
miamining.com
andmining.nyc
could be co-hosted under the domainexplorecitycoins.com
or with subdomains like the examples above.Another alternative would be to standardize the naming of these sites.
miamining.com
andmining.nyc
are different, which can cause confusion. Standardization of 'CityIDmining.com' or 'mining.CityID', not both.Additional context Add any other context or screenshots about the feature request here.