Repository navigation
Remove bit.ly links from template #5910
Description
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?
Activity
bondz commentedon Nov 27, 2018
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.
iansu commentedon Nov 27, 2018
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.
bondz commentedon Nov 27, 2018
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.
iansu commentedon Nov 27, 2018
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. 😞
stale commentedon Dec 29, 2018
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.
petetnt commentedon Dec 30, 2018
We could use Netlify's
__redirectsfile to do the short links similar to @kentcdodds netlify-shortenerThis would give us
The usage is rather simple, a
__redirectsfile in the root redirects (with 301s or 302) or rewrites relative and absolute URLs according to the specification that looks something like this:only thing missing would be the domain name :)
iansu commentedon Dec 30, 2018
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.
stale commentedon Feb 7, 2019
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.
stale commentedon Mar 9, 2019
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.
1 remaining item
stale commentedon Apr 9, 2019
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.
pimlottc-gov commentedon Jul 3, 2019
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?
nel417 commentedon Feb 27, 2020
any action on this?
mikeperrotta commentedon Apr 28, 2021
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.