SupaKewber publishes product documentation, troubleshooting, lessons, algorithm training and data analysis. Those formats need different evidence, but all visible content should distinguish measured fact, documented behavior, practical recommendation and interpretation.
Core standards
What every page should do
Answer directly
State the useful answer early, then give its conditions and evidence.
Name the source
Separate product tests and practice data from browser documents and WCA results.
Show limits
Do not turn model-specific compatibility or a small sample into a universal claim.
Keep it current
Date meaningful revisions when browsers, firmware or the product change.
Evidence order
Sources used for technical and learning content
- Observed product behavior: current code, repeatable tests and supported protocol behavior.
- Primary documentation: official browser documentation, technical specifications and WCA data or regulations.
- First-party aggregate data: privacy-thresholded practice, trainer, connection and competition data with a method.
- Practical judgement: training recommendations identified as advice rather than official rules.
Competitor pages can identify a question, but they are not primary proof of how SupaKewber or a device behaves.
Training content
Algorithms are more than a move string
Algorithm pages should show recognition, setup, primary and alternative executions, finger tricks, common mistakes, related cases and a trainer. Learning order and difficulty are practical recommendations, not official rankings.
Different hands, grips and turning styles can make a valid alternative better for a particular cuber. One algorithm is not presented as the only correct choice when credible alternatives exist.
Independence
Product coverage is not endorsement
SupaKewber is independent and not affiliated with GAN or the WCA. Device names and trademarks identify compatible products and official sources.
If sponsorship, affiliate compensation, gifted hardware or another material relationship influences a future page, it will be disclosed prominently on that page. No relationship should be inferred merely because a product is supported.
Corrections
How errors and disagreements are handled
Report errors through the contact page with the page URL, disputed statement, relevant cube or browser version and reproducible evidence.
Typographical fixes may be silent. A change that alters compatibility, a calculation, dataset result or central recommendation should update the visible modified date and explain the change when useful.