-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Remove bit.ly links from template #5910
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
Comments
As discussed in the previous thread. I prefer firebase page.link dynamic links which would generate shortened links like https://cra.page.link/docs and allows us change the target destination as well. I am open to transferring it to a maintainer once we agree on what to do. |
I somehow missed that suggestion in the previous thread. Seems like an okay option. Depending on anything Google related long-term worries me a bit though. What would be really great is if Docusaurus supported shortlinks/aliases and we could use those instead. That combined with a custom URL for Create React App would be really nice. Not sure how feasible that is though. |
Docusaurus supporting this natively would be best and that could be taken upstream and would take a while if they decide to add that. Thought of getting create-react.app and createreact.app but they are both taken. |
Yeah, @Timer and I noticed createreact.app was taken. Sad that neither of them are being used. A bunch of other CRA related domains are also being squatted. 😞 |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
We could use Netlify's This would give us
The usage is rather simple, a /cra /create-react-app
/cra2 /foobar 302
/fOb https://facebook.github.io/create-react-app/docs/setting-up-your-editor
/google https://www.google.com only thing missing would be the domain name :) |
I think this is a pretty good option, provided we get our own domain name. It's nice to not be tied to any particular shortening service. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
I appreciate the thoughtful discussion on a better long term solution, but in meantime, documentation links have broken for months. Perhaps just create new bit.ly links for now and replace them with more durable links later? |
any action on this? |
Just noticing the links are still old and wanted to echo @pimlottc-gov's comment. There's lots of very thoughtful discussion here, but it might be good to sub in a bit.ly link in the meantime if this isn't moving forward. Could be a case of perfect being the enemy of good. |
We need to remove the bit.ly links from the template because they point to the old README. We need to decide what to replace them with though. We could pick a new URL shortner but we could wind up in this situation again. Some allow you to change link destinations but who would own that account?
Follow up to: #5808.
Related: #5536
The text was updated successfully, but these errors were encountered: