feat: modified/added meta tags with new content

[jordanh]

Description

Closes #9407

Testing scenarios

• Navigate to Sign-Up Page

  • Note and proofread new meta

• Navigate to Create Account Page

  • Note and proofread new meta

• Share an invitation link

  • Note and proofread new meta

• Share any other URL

  • Note and proofread new meta

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label Skip Maintainer Review Indicating the PR only requires reviewer review and can be merged right after it's approved if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog

[Dschoordsch]

I'm not sure what the goal of some of the changes is. If we want to have a nice preview in Slack etc. for different routes, I think there is no way around serving different versions of index.html based on route, so we could have 1 generic, 1 for mass invite and 1 for team invite?
Let me know if I'm just missing something here.

[jordanh]

I'm not sure what the goal of some of the changes is. If we want to have a nice preview in Slack etc. for different routes, I think there is no way around serving different versions of index.html based on route, so we could have 1 generic, 1 for mass invite and 1 for team invite? Let me know if I'm just missing something here.

I was following work from here: https://www.notion.so/parabol/c8419b4417324a8cae36570631e62beb?v=c18a873d44014bc3ab24eb850e325771&pvs=4

Your comments make sense to me.

I am going to adjust the goal of this work to simply update the meta text to broaden our intent slightly beyond agile for unauthenticated routes and back the rest of the changes out.

[jordanh]

@Dschoordsch thank you for the review! I updated based upon your comments

[Dschoordsch]

@jordanh Please next time press the "Re-request review" button as I might miss mentions.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ Error: Rendered more hooks than during the previous render. useDocumentTitle(packages/client/hooks/useDocum... View Issue

_{Did you find this useful? React with a 👍 or 👎}