Building a track is half the fun of an editor-based racer. Getting other people to actually play it is the other half. A little presentation goes a long way.
Test before sharing
Drive your track several times from a cold start. Check that every checkpoint triggers, the finish is reachable, and nothing relies on a lucky bounce.
Give it a clear name
"Track 7" tells nobody anything. A short name that hints at the style, like "Canyon Sprint" or "Loop Gauntlet", helps players choose.
Write a one-line description
Say what kind of track it is: short and technical, long and fast, or jump-heavy. Mention the difficulty honestly.
Post your target time
A target or author time gives players something to chase and shows the track is beatable.
Copy the code carefully
Track codes are long strings. Paste them into a plain-text spot; some chat apps add formatting or cut long messages. Test the code yourself by importing it into a fresh session.
Credit inspirations
If your track remixes someone else's idea, say so. Communities around small games stay friendly when people credit each other.
Need a refresher on moving codes in and out of the game? How to import tracks on ThePolyTrack walks through it step by step.
Disclosure: written by an independent PolyTrack fan site (thepolytrack.com), not the game's developer.