Robolyst Robolyst
The whole toolkit A public site sponsors can take seriously

Team websites

Sponsors look you up before they reply. A dead Wix page from three seasons ago is worse than no page, and a team site is exactly the kind of thing that stops being maintained the moment the student who built it graduates.

Try it in the live demo

Free for every team · run by a 501(c)(3)

A team page assembled from blocks, on your own domain.

team1234.org Domain verified
Cedar Bots · FTC 1234 Eleven seasons out of one high-school shop.
11 seasons
4 Inspire awards
38 outreach hrs
26 members
Sponsors · title tier
TitleGoldGoldCommunity
Contact form: submissions land in the portal
Own sitemap and search presence · Per-page view counts · No third-party tracker

On screen

The page itself, captured out of the live demo, which anyone can open, without an account.

A public Robolyst FTC team page: team number, location, career record, awards, robot photo and sponsors on one page.
Every team gets a public page; teams that want more get a full site.

Edit it without knowing HTML

Pages are built from blocks (text, images, galleries, sponsor walls, forms) arranged in an editor. A new webmaster can pick it up in an afternoon.

Nothing is public until you say so

A new site is a draft. You build it, look at it, show a mentor, and publish when it is ready. Half a homepage is never the thing a sponsor finds while you are still working on it, and a site can go back to draft later without being deleted.

Your own domain

Point team1234.org at your site and it serves from there, with its own sitemap and its own search presence. No Robolyst branding in the URL.

The things a team site actually needs

Not a generic page builder. The blocks are the ones a robotics team keeps rebuilding by hand.

  • A sponsor wall with tiers, driven by the same sponsor list the rest of the portal uses
  • Contact and interest forms that land in the portal rather than an inbox nobody checks
  • Your competition results, pulled live from the archive
  • A donation page, and a ledger block for teams that publish where the money went
  • Visitor analytics, without embedding a third-party tracker on a site students visit

Publish what you built

Post a release (CAD, code, a scouting spreadsheet, an outreach curriculum) as files or a repo link, and it goes into the public open-source directory where teams find each other’s work and vote the useful things up. Downloads are counted per project, so “did anyone use this” has an answer.

For the site you already have

Plenty of teams are stuck on a school page or a Wix site nobody can move. Embeds put your live record on it anyway: pick blocks, arrange them, copy the snippet. The whole design travels in the link, so there is nothing to host and it keeps working when the student who made it graduates.

  • Rankings, next match, award list, season stats, sponsor reel, a live event ticker
  • Ready-made snippets for Notion, WordPress, Wix, Squarespace, Google Sites and OBS
  • A QR code for the ones that end up on a pit banner
  • Themed to your colours, and legible on a light page or a dark one

It stays up

Hosting, certificates and updates are handled. The site does not go down because a card expired over the summer.

Questions teams ask

Is the website free?
Yes, including hosting. A custom domain is the one thing you buy yourself, from any registrar.
Can we use our existing domain?
Yes. Point it at the site and verify it from the portal. Until it is verified the site stays reachable at its Robolyst address.
Do visitors get tracked?
Page views are counted for your own analytics. There is no third-party advertising tracker on team sites.
When does the site go live?
When you publish it. A site starts as a draft that only your team can open, so there is no window where an unfinished page is the first thing a sponsor sees. Unpublishing puts it back without losing anything.
We already have a site we cannot replace. Is any of this useful?
The embeds are. Build a block of your rankings, your next match or your sponsor wall and paste one snippet into whatever you are stuck with, including a school CMS you do not control. The configuration is in the link, so nothing has to be hosted or maintained on your end.

Team websites is one part of the portal.

The roster, the build schedule, your documentation, the money and your public site run on the same free account. Setting it up takes an afternoon.

Try it in the live demo