Add a link for a standalone version of the form.

[freakboy3742]

Provide an explicit link for the mailing list signup form, as a fallback when users have issues with the embedded form.

Fixes #607.

PR Checklist:

• All new features have been tested
• All new features have been documented
• I have read the CONTRIBUTING.md file
• I will abide by the code of conduct

[github-actions]

Visit the preview URL for this PR (updated for commit b00f9c9):

https://beeware-org--pr610-members-link-tuclgwaq.web.app

_{(expires Wed, 23 Apr 2025 00:13:43 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: b0da44bc067e7d9a4255c77cb2c5fce572218cec}

[mhsmith]

If a user fills in the the embedded form and it fails to submit, then there's a pretty good chance that they'll give up immediately rather than go to the trouble of filling it in again on the standalone page. And that's assuming they even notice the new link.

How about we remove the embedded form, and keep the link to the standalone form that we know always works? It has slightly better formatting as well.

[freakboy3742]

If a user fills in the the embedded form and it fails to submit, then there's a pretty good chance that they'll give up immediately rather than go to the trouble of filling it in again on the standalone page. And that's assuming they even notice the new link.

Yeah - I'll freely admit I don't especially like the link option.

How about we remove the embedded form, and keep the link to the standalone form that we know always works? It has slightly better formatting as well.

It does - but it means linking off to a completely different site, and there's no obvious "return" path. My concern is the broader UX here. If it's just a link, then we're going to end up fighting the back button on a form submission; if we open a new window/tab, anyone with popup suppression might not see the form at all.

[mhsmith]

but it means linking off to a completely different site, and there's no obvious "return" path.

It does take you back to the BeeWare site afterwards, albeit via the pybee.org domain:

We could change that to a more specific page like keep-informed.

The Mailchimp form also contains "Windows Phone", which I guess we should remove.

Apart from that, its UX seems fine to me.

[freakboy3742]

but it means linking off to a completely different site, and there's no obvious "return" path.

It does take you back to the BeeWare site afterwards, albeit via the pybee.org domain:

I've reconfigured the Mailchimp form to use beeware.org, and remove the Windows Phone option; given that there's a clear return path, I've replaced the entire community/keep-informed page with a redirect to the mailing list form.

[mhsmith]

Unfortunately it looks like this has removed the page entirely from the Community index page.

Also, it loses the link to Mastodon. I know there's a link in the footer of every page, but I don't know if you wanted it to be a bit more prominent in this context?

[freakboy3742]

Ugh... I wasn't overly concerned about losing the Mastodon link - but I missed that it would lose the page on the Community index as well. Take 3...