-
Notifications
You must be signed in to change notification settings - Fork 66
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
Docs: Clearer DNS instructions and cross-linking #4886
Conversation
Technically it looks fine. You can merge it whenever you feel it's ready to be made publicly available. |
How does it though? Currently, step 1 is setup a DNS server and get yourself a domain, which is a big step putting off 93% of visitors... the plan here is to provide the non-DNS route for quicker onboarding? I'd even go as far as saying bin DNS option in quick start entirely, and just present the non-DNS option |
The current approach requires one to have a Fully Qualified Domain Name with the possibility to modify its DNS records. It does not require to setup a DNS server. I might be wrong, but I feel that we might not benefit much from this change. On the other hand, given the high failure rate, we probably won’t lose much either. |
@joepavitt Can we publish this? |
@joepavitt @ppawlowski do we know what this is waiting on? Can it be merged and iterated on if needed? |
I shared my concerns but I'm ok to merge changes if others gave approvals. |
Let's merge this and iterate where appropriate |
Description
We're losing an estimated 93% of traffic to the first step in our self-hosted install instructions for our "Quick Start" guide. This attempts to remedy the step/intimidation of setting up a DNS server in Step 1, which will hopefully improve conversion here.