About the team

Same flock.
Cleaner line.

Team Duckies is the next public identity for a team that already built a roster, member culture, website, setup garage, and recognizable duck mascot together.

The rebrand is not intended to erase the original team. It gives that work a name and visual system better suited to sponsors, search, and modern public platforms.

Team story

Team Duckies grew from a player-led racing team with a distinct mascot, individual member artwork, competitive identity, and a desire to share useful information instead of operating only through scattered chat messages.

The new website direction puts the team, members, cars, accomplishments, and partners first. The Player Garage remains because setup sharing solves a real community need.

Formerly Bloody Duckies

Team Duckies was formerly known as Bloody Duckies.

The previous name remains an important part of the team’s history. The transition is intended to improve sponsorship compatibility, search clarity, and social-platform presentation while retaining the duck identity and existing community recognition.

Team principles

  • Competition with accountability: results and claims should be verifiable.
  • Shared knowledge: useful public setups should be easy to find and understand.
  • Respect for private work: unlisted setups stay controlled by their creators and share codes.
  • People over dashboards: real members and vehicles carry the public story.
  • Professional without becoming generic: the duck remains part of the team identity.

Privacy approach

The less data the site gathers, the less data it can misuse, leak, or burden the team with protecting. Public pages should work without an account. Analytics should be minimal and privacy-respecting. Private setup access should require a code, not a viewer profile.

Website direction

This proof of concept is intentionally static and dependency-light. It can later be implemented in WordPress using the existing roster and garage plugins, or serve as the front end for a small custom CMS. The content model—not the CMS vendor—should determine the design.