Skip to content
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

Impact Page #238

Closed
wants to merge 3 commits into from
Closed

Impact Page #238

wants to merge 3 commits into from

Conversation

mattxwang
Copy link
Member

@mattxwang mattxwang commented Aug 12, 2021

@mattxwang mattxwang marked this pull request as draft August 12, 2021 21:25
@mattxwang mattxwang changed the title Matt's Draft Impact Page Impact Page Aug 18, 2021
mattxwang added a commit that referenced this pull request Aug 20, 2021
This PR implements per-page SEO tags via [`next-seo`](https://github.com/garmeeh/next-seo). Under-the-hood, the package handles basic meta tags, and OpenGraph URLs; according to the documentation, Twitter now also parses OG data, and thus doesn't generate twitter-specific metadata.

I then manually write and apply copy for each page: the home page, about, committees, events, sponsors, and tech gala. We'll have to backport this to other new pages, like the ones introduced in #238 and #235. I chose not to add any default templating or abstract this to a component, since I think the copy differs enough where boilerplate doesn't help us too much.

For reviewers - it would be great if you could test this on a variety of social media platforms (Facebook, Twitter, Discord, Instagram. etc.). I've done Discord testing in the #test3 moderator channel of the server, as well as DMing myself on FB messenger.

Closes #116, (hopefully) closes #194.
mattxwang added a commit that referenced this pull request Aug 20, 2021
This PR implements per-page SEO tags via [`next-seo`](https://github.com/garmeeh/next-seo). Under-the-hood, the package handles basic meta tags, and OpenGraph URLs; according to the documentation, Twitter now also parses OG data, and thus doesn't generate twitter-specific metadata.

I then manually write and apply copy for each page: the home page, about, committees, events, sponsors, and tech gala. We'll have to backport this to other new pages, like the ones introduced in #238 and #235. I chose not to add any default templating or abstract this to a component, since I think the copy differs enough where boilerplate doesn't help us too much.

For reviewers - it would be great if you could test this on a variety of social media platforms (Facebook, Twitter, Discord, Instagram. etc.). I've done Discord testing in the #test3 moderator channel of the server, as well as DMing myself on FB messenger.

Closes #116, (hopefully) closes #194.
@tnawathe21 tnawathe21 mentioned this pull request Sep 2, 2021
@mattxwang
Copy link
Member Author

Superseded by #260

@mattxwang mattxwang closed this Sep 3, 2021
@mattxwang mattxwang deleted the impact-page-matt branch September 27, 2021 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants