You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
js.org has a DNS service that provides short URLs that can point to websites. I think nodeos.js.org or node-os.js.org would sound a lot cooler and more relevant to this project. I'm not here to say that node-os.com is in any way undervalued or am I saying that it should be.
Since the website is mostly static (except for the blog that is powered by Github issues with ci-blog), I don't see any use for a standalone domain that serves only the static website. This is where the js.orgDNS service should align very well. This could also save the costs for maintaining the domain (even though it shouldn't be quite the hassle).
The only change that needs to be done from our part is to change the existing CNAME file in the root of the repository that would point to the new domain.
I can create a pull request for modifying the existing CNAME file for the custom sub-domain as well the pull request to js-org/dns.js.org to assign the sub-domain to node-os.
I'm asking approval / permission to do these 👆 for node-os.
Also, we need to decide on which domain to use. Personally, I think node-os.js.org would look better than nodeos.js.org, but I'll leave it up to you to decide which subdomain you'd like to use.
The text was updated successfully, but these errors were encountered:
js.org has a DNS service that provides short URLs that can point to websites. I think nodeos.js.org or node-os.js.org would sound a lot cooler and more relevant to this project. I'm not here to say that node-os.com is in any way undervalued or am I saying that it should be.
Since the website is mostly static (except for the blog that is powered by Github issues with ci-blog), I don't see any use for a standalone domain that serves only the static website. This is where the js.org DNS service should align very well. This could also save the costs for maintaining the domain (even though it shouldn't be quite the hassle).
The only change that needs to be done from our part is to change the existing CNAME file in the root of the repository that would point to the new domain.
I can create a pull request for modifying the existing CNAME file for the custom sub-domain as well the pull request to js-org/dns.js.org to assign the sub-domain to node-os.
I'm asking approval / permission to do these 👆 for node-os.
Also, we need to decide on which domain to use. Personally, I think node-os.js.org would look better than nodeos.js.org, but I'll leave it up to you to decide which subdomain you'd like to use.
The text was updated successfully, but these errors were encountered: