Update compare pages

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

WARNING ⚠️ this PR is very large, summary may not cover all changes.

🌟 Summary

Big refresh of DAMO-YOLO comparison docs with clearer structure, richer context, and stronger guidance toward modern Ultralytics options like YOLO26 🚀📚

📊 Key Changes

• Rewrote multiple comparison pages (DAMO-YOLO vs EfficientDet / PP-YOLOE+ / RTDETRv2 / YOLO11 / YOLO26 / YOLOv10 / YOLOv5 / YOLOv6 / YOLOv7) with updated intros, headings, and organization ✍️
• Added/expanded model overviews (authors, dates, links, key architectural features) for DAMO-YOLO and competitors 🧠🔍
• Improved benchmark sections with clearer performance tables, highlighting best-in-row metrics and adding interpretive “Analysis” callouts 📈⏱️
• Added more practical sections like use-case recommendations (when to pick each model) and “strengths/weaknesses” guidance 🎯🛠️
• Strengthened cross-linking to Ultralytics resources (e.g., YOLO26, YOLO11, integrations like TensorRT/ONNX, and the Ultralytics Platform) 🔗🌐
• Included more “developer experience” content (Python snippets showing training/export with Ultralytics) 👩‍💻⚡

🎯 Purpose & Impact

• Makes the comparison pages more readable and educational for both newcomers and experienced users by separating “overview → benchmarks → analysis → use cases” 🧩📖
• Helps users make deployment-minded decisions (latency vs accuracy vs ecosystem friction) rather than relying only on headline mAP numbers 🏁📊
• Reinforces YOLO26 as the recommended modern default (NMS-free, edge/CPU focus, streamlined workflow) which may guide readers toward faster adoption of Ultralytics tooling 🚀✅
• Improves discoverability of related docs and tooling (exports, integrations, Platform) which can reduce time-to-train and time-to-deploy for real projects ⏳🔧

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview, Comment	Jan 25, 2026 11:54pm

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/docs 🚀 PR! This is an automated message to help streamline review; an engineer will assist soon. ✅

-✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
-✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/docs main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
-✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
-✅ Update Documentation: Update the relevant documentation for any new or modified features.
-✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
-✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
-✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Overall the content updates look solid and consistent with the refreshed narrative. Only minor doc hygiene issues found around raw-URL link text; recommend switching to descriptive anchor text to match project guidelines.

💬 Posted 2 inline comments

⚠️ Large PR: Review focused on critical issues. Some details may not be covered.

[UltralyticsAssistant]

Merged and looking fantastic — thank you @glenn-jocher for the huge refresh across the DAMO-YOLO comparison docs. The clearer “overview → benchmarks → analysis → use cases” flow makes these pages dramatically more approachable, and the stronger guidance toward modern Ultralytics defaults like YOLO26 will help readers make faster, more deployment-minded decisions.

“If I have seen further it is by standing on the shoulders of giants.” — Isaac Newton

This PR really embodies that idea: it builds on the community’s prior work and turns it into a sharper, more educational reference that helps users choose the right model, adopt YOLO26 with confidence, and move from reading to training/deploying sooner (especially with the Ultralytics Platform). Appreciate the care and clarity you brought to a large, high-impact set of docs.