[DRAFT] feat(landing): Playpond link.

[aidanCQ]

[hugrbot]

Hey there and thank you for opening this pull request! 👋

We follow the Conventional Commits convention for PR titles. It looks like your title needs some adjustment.

The title should have a type prefix, followed by a colon. The most important ones are:

• feat: for new features
• fix: for bug fixes

If the PR contains a breaking change, use feat!: or fix!: instead and include a "BREAKING CHANGE:" footer in the description of the pull request.

You may also include a (scope) after the type prefix.

Expand this message for the full list of tags.

• feat: New feature
• fix: Bug fix
• docs: Documentation-only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc)
• refactor: A code change that neither fixes a bug nor adds a feature
• perf: Performance improvements
• test: Adding missing or correcting existing tests
• ci: Changes to our CI configuration files and scripts
• chore: Other changes that do not alter public APIs or code behaviour
• revert: Reverts a previous commit