Add more detail and examples to redirect guidance

[yndajas]

This explains the different uses of the two redirect methods in more detail, and provides examples of situations in which you would each one

[netlify]

✅ Deploy Preview for laughing-payne-b9fbd2 ready!

Name	Link
🔨 Latest commit	801609a
🔍 Latest deploy log	https://app.netlify.com/sites/laughing-payne-b9fbd2/deploys/63dd2f39ae13730009d5f59a
😎 Deploy Preview	https://deploy-preview-1071--laughing-payne-b9fbd2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[snim2]

This looks good to me, and I don't want to block it from being merged, but I wonder whether we need a slightly different set of docs for colleagues who use the CMS on the README?

[yndajas]

This looks good to me, and I don't want to block it from being merged, but I wonder whether we need a slightly different set of docs for colleagues who use the CMS on the README?

Do you mean we'd move any detailed stuff for devs more into the README, and leave the rest (CMS) in the contributing guide?

[snim2]

This looks good to me, and I don't want to block it from being merged, but I wonder whether we need a slightly different set of docs for colleagues who use the CMS on the README?

Do you mean we'd move any detailed stuff for devs more into the README, and leave the rest (CMS) in the contributing guide?

Oh that's a really good point. I guess non-technical people will look at the site and not the README?

[yndajas]

Oh that's a really good point. I guess non-technical people will look at the site and not the README?

I'd guess so! Might be worth adding an issue to review/pick this up separately?