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
The sh TLD is for a country and it's a bad practice to use those. I have purchased getporter.org, which also helps reinforce our getporter brand on most of our sites (github, docker hub, ghcr.io, twitter).
Let's start using getporter.org instead, move the registration to the CNCF and see if we can use netlify to redirect porter.sh to getporter.org.
I am adding this to the v1 timeline because it's a disruptive brand change that I'd like to have done before we do any big content pushes with the old domain.
The text was updated successfully, but these errors were encountered:
Another question is how/when do we want to make the 1.0.0 docs the default on the website? I was thinking cutting over when we reach 1.0.0-beta.1, so that people start seeing a version that is supported through 1.0.0 and new people don't start with v0.38.
Let's cname getporter.org -> release-v1.porter.sh and start giving that to people instead of the version specific URL. Then at 1.0 we can switch to getporter.org for everything.
The sh TLD is for a country and it's a bad practice to use those. I have purchased getporter.org, which also helps reinforce our getporter brand on most of our sites (github, docker hub, ghcr.io, twitter).
Let's start using getporter.org instead, move the registration to the CNCF and see if we can use netlify to redirect porter.sh to getporter.org.
I am adding this to the v1 timeline because it's a disruptive brand change that I'd like to have done before we do any big content pushes with the old domain.
The text was updated successfully, but these errors were encountered: