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

Support: New page #237

Merged
merged 1 commit into from
Mar 30, 2024
Merged

Support: New page #237

merged 1 commit into from
Mar 30, 2024

Conversation

Krinkle
Copy link
Member

@Krinkle Krinkle commented Oct 14, 2023

@timmywil
Copy link
Member

So, the objective is to redirect all jquery.org pages somewhere else and remove the jquery.org droplet? I'm okay with that, but we should make sure jquery.org/404 redirects.

@Krinkle
Copy link
Member Author

Krinkle commented Oct 16, 2023

So, the objective is to redirect all jquery.org pages somewhere else and remove the jquery.org droplet? I'm okay with that, but we should make sure jquery.org/404 redirects.

We don't have dedicated server droplets for individual domains. We have two servers (wp-04, wp-05) which each have a complete set of databases and are each able to respond and generate any WordPress page on any virtual host.

But yes, I think our objective is move content to places where it feels more "current" and also more easily updated/searched/discovered and yields more benefit/value by being part of the picture. If we can remove the jquery.org theme from jquery-wp-content, and replace jquery.org in Puppet with a simple set of redirects (no extra WP install) that'd reduce maintenance a little bit, bit that's not the motivation. We have enough automation in place that an extra domain or fewer doesn't make much difference.

I was operating on the assumption that it's a shared goal in its own right to phase out serving pages under "jquery.org". Please do question or challenge that if you have other ideas for what we could do there!

@Krinkle Krinkle force-pushed the support-page branch 3 times, most recently from fdc0cc9 to 8cb42c9 Compare October 16, 2023 17:40
@timmywil
Copy link
Member

Yeah, I shouldn't have said droplet; theme and virtual host.

@Krinkle Krinkle force-pushed the support-page branch 4 times, most recently from e061c52 to 2f1adb4 Compare October 26, 2023 06:12
@Krinkle
Copy link
Member Author

Krinkle commented Mar 29, 2024

updated to reflect the email address changes from jquery/brand.jquery.org@1d6c34e.

@timmywil Is this good to go?

Once live, I propose we redirect these two URLs to this new page at https://jquery.com/support/:

Then in the site header:

And in the site footer:

Copy link
Member

@timmywil timmywil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Krinkle Krinkle merged commit ddd2762 into main Mar 30, 2024
1 check passed
@Krinkle Krinkle deleted the support-page branch March 30, 2024 21:58
Krinkle added a commit to jquery/jquery.org that referenced this pull request Mar 30, 2024
Krinkle added a commit to jquery/brand.jquery.org that referenced this pull request Mar 30, 2024
Krinkle added a commit to jquery/jquery-wp-content that referenced this pull request Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants