CONTACT FORMULA BREAKING
We welcome feedback, feature ideas, and questions about the tools. The fastest way to get in touch is through GitHub, where issues and feature requests are tracked publicly.
If you are reaching out about a publishing workflow, include the type of race-weekend content you are producing and where your process currently breaks down. Clear context helps us respond with practical recommendations and prioritize updates that improve the overall value of the platform for serious creators.
We especially value feedback that includes examples, expected outcomes, and constraints. That level of detail helps us separate one-off preferences from recurring workflow needs and ship updates that improve reliability across many different creator setups.
Reach Us on GitHub
If you have a bug report, feature idea, or improvement request, open an issue or start a discussion on GitHub. Include screenshots or links when possible so we can reproduce the problem quickly.
Visit GitHub ProfileWhat to Include
- Which tool you used (breaking news or starting grid)
- Steps to reproduce the issue, if relevant
- Screenshots or exported images
- Browser and device information
Helpful Links
You can also review the About page for project details or check the Privacy Policy to learn how data is handled.
Response and Editorial Requests
We use contact requests to prioritize roadmap work and editorial updates. If you are reporting a bug, include the expected behavior and what happened instead. If you are requesting a template or content guide, include the race-weekend scenario you are trying to cover so we can evaluate whether it fits the product direction.
For collaboration requests, include your channel type, target audience, and desired output format. Clear details help us respond faster and improve the quality of future posts, tools, and creator resources published on the site.
We read every serious request and use recurring feedback patterns to prioritize updates. Detailed reports directly influence bug fixes, template improvements, and future educational content published across the blog.