Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Domain Recipes: clarify allowed tlds for recipe 1 and other suggestions #139

Open
maxime-memtell opened this issue Jun 14, 2022 · 0 comments

Comments

@maxime-memtell
Copy link

maxime-memtell commented Jun 14, 2022

General Description

As a reader of the "Domain Recipes" page I would like to have more clarity as to which tlds are ok for recipe 1 in order to have 0 doubt on whether I can buy a domain on Route 53 and get started.

In more details

As I was following the quick start guide and went through the domain recipes, in particular recipe 1, I found the documentation text to be just a tiny bit unclear on the fact that ".com" and ".link" are placeholders, and can be replaced by other top-level domains (tld), say ".io" or ".co", and since this step costs money, it could/should be improved.

Small hints that overall created my doubt:

  • ".link" is a very specific tld and is not necessarily a short one for what is supposed to be a short link
  • There is a bit on second-level domains and their specificity
  • Nowhere is it explicitly said that ".com" and ".link" are placeholders

I eventually went forward and can clarify that it is indeed perfectly ok to have a ".co" instead of ".com" for instance, while using Recipe 1.

Potential solution:

Currently, it writes:

Known bug + fix: Using a second level domain (.co.uk, .com.fr, etc)? Use Recipe 3.

Instead it could write:

".com" and ".link" can be replaced by other top-level domains at your convenience, eg. ".co", ".io" etc.
Known bug + fix: Using a second level domain (.co.uk, .com.fr, etc)? Use Recipe 3.

Aside from this, I also found:

  • It was hard to guess what the short-link link does exactly. Again, the ".link" example threw me off track for a sec since it's not that short and actually longer in the example ("myhub.com" vs "myhub.link"). An illustration (screenshot), and/or a reference to the Mozilla example could be helpful ("hubs.mozilla.com" vs "hub.link")
  • Someone on discord warning me that which tld to chose is also important for email server spam filters. In particular that ".space" was an issue for them
  • There are leftovers from drafts/todo in the doc? For instance

mysite.com set up on on Route 53 (?)

What is the (?) doing here?

  • While following Recipe 1 it was not clear when I should instantiate on a subdomain

I would be happy to submit a quick PR if someone doubles-check my language prior to it since I am not a native English speaker.

Let me know what I can clarify, in the meantime, my domains got approved, the transfer lock got disabled and my stack got successfully deployed 🎉 😄

@maxime-memtell maxime-memtell changed the title Domain Recipes: clarify allowed tlds for recipe 1 Domain Recipes: clarify allowed tlds for recipe 1 and other suggestions Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant