Restore articles and Vercel Web Analytics - #13
Merged
Conversation
- Models (/models): families grouped by architecture (CNN vs DETR), each links to its existing (previously unlinked) family page - Articles (/articles): in-shell section + one sample article that embeds a live verified chart; MDX-ready content registry - Homepage: shields-style Benchmark runs badge from the verified dataset; reframe as LibreYOLO's board and drop the 'most models' hedge - Nav adds Models + Articles; pin turbopack.root to stop stray home-dir lockfiles misdirecting Next's workspace root
- Benchmark runs badge: add hover tooltip explaining the count spans model sizes, hardware, and runtimes (client component) - Models page: drop non-LibreYOLO baseline families and remove the Approach column
…to sitemap Mechanistic step computes facts + significance-gated claims from the verified dataset; LLM writes only validated prose slots; data blocks render live. Includes article-v2 skill for writer subagents and a demo vs article (dfine-s-vs-yolov9s) proving the pipeline end to end.
…ides, license guide, FP16 finding, 4 vs comparisons All written by writer subagents against gated claims files and validated (numbers sourced, style lint, prose budget). Sitemap picks them up automatically.
Scores every viable article by demand (popular families) + differentiation (cross-family, ranking flips, license edges) and penalizes repeated family+size shapes so near-duplicates sink. Documents wave-based scaling in the skill to avoid site-wide Helpful-Content demotion.
… + 3 license guides, 30 cross-family vs pages) Selected via claims.py plan (demand+differentiation scored, near-duplicate penalized), written by 6 writer subagents against gated claims files, each independently re-validated. Site now at 52 engine-authored articles + 1 legacy. Sitemap auto-updated.
…, prune redundant variant pages New family-vs claims type pairs variants across two architecture families by nearest params and reports the matched-compute accuracy edge, speed edge, and frontier crossover. New family-frontier data block renders both variant ladders live. Published 15 family comparisons (the head-term layer). Set 27 model-variant vs pages whose family pair is now covered to draft (kept in repo, out of sitemap), plus the legacy yolov9s-vs-yolox-s. Net published: 40 (15 family-vs, 8 long-tail vs, 16 guides, 1 finding).
Expands verified-results.v1.json and adds 131 raw rpi5/jetson/hailo submissions, the rpi5_hailo8 hardware and hailo_int8 runtime definitions, corrects YOLO-NAS license to non-permissive, adds @vercel/analytics. These back the hardware, license, and family articles just shipped. Also gitignores build logs and agent worktrees.
Contributor
Author
|
Verified Vercel preview: https://website-7um05xgak-xubanceccons-projects.vercel.app Authenticated smoke tests returned 200 for /, /articles, /models, /articles/yolov9-vs-yolox, and /sitemap.xml. The hosted client bundle contains @vercel/analytics. The automatic Git connection remains blocked because the Vercel GitHub App does not currently have access to the LibreYOLO organization repository. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/articles,/models, and 39 currently published article routesmaininstead of replacing newer benchmark and reproducibility work@vercel/analyticsand the root<Analytics />componentRoot cause
The article work lived only on
feat/models-articles-proposal. Later production CLI deployments came frompublish-ultralytics-benchmarksandadd-segmentation-page, which did not contain either the article routes or Analytics. That replaced the tracked production build and caused Vercel Web Analytics to fall to zero.Validation
python scripts/build_verified_results.pynpm testarticle-pipeline/v2/validate.pynpm run lint --prefix websitenpm run verify:analytics --prefix websitenpm run buildbuilds 510 pages successfully/,/articles,/models, a generated article, and/sitemap.xmlall return 200Deployment note
After merge, production should be deployed from the repository root. The Vercel project should also be linked to this GitHub repository with
mainas its production branch so stale CLI branches cannot silently replace production again.