Threads 22: Publish the threads product page - #251
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Sorry @FranciscoMoretti, you have reached your weekly rate limit of 500000 diff characters.
Please try again later or upgrade to continue using Sourcery
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Greptile SummaryThis PR publishes the Threads product page at
Confidence Score: 5/5Safe to merge — the change is entirely additive (new page, new nav/footer entry, new sitemap entry) with no modifications to existing logic or data flows. All changed files are purely additive: a new static page, a new constant in site-config, and one-line additions to the navbar, footer, and sitemap. The hardcoded path and date issues were already raised in a prior review round and carry no runtime impact. Nothing here touches shared state, authentication, data fetching, or existing routes. Files Needing Attention: No files require special attention beyond what was already flagged in the previous review round. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[User] -->|navigates| B[Navbar: Threads link]
B --> C[Threads Page]
C --> D[Hero: useChat migration diff]
C --> E[ThreadInstallCommand]
C --> F[Playground: ThreadPlayground]
C --> G[Compatibility and Additions section]
C --> H[Architecture section]
C --> I[CTA: integration guide]
J[sitemap.ts] -->|url: siteLinks.threads| C
K[site-config.ts: siteLinks.threads] --> J
K --> C
L[footer.tsx: useThread link] --> C
style C fill:#f0f4ff,stroke:#6366f1
style K fill:#fef9c3,stroke:#ca8a04
Reviews (38): Last reviewed commit: "feat(site): publish the threads product ..." | Re-trigger Greptile |
| { | ||
| url: siteLinks.threads, | ||
| lastModified: new Date("2026-07-10T00:00:00.000Z"), | ||
| changeFrequency: "weekly", | ||
| priority: 0.9, | ||
| }, |
There was a problem hiding this comment.
The threads entry uses a one-off hardcoded date while every other sitemap entry uses the shared
siteLastModified constant. When the site is next updated and siteLastModified is bumped, the threads page will report a stale modification date to search engines, potentially hurting its crawl priority relative to the other pages.
| { | |
| url: siteLinks.threads, | |
| lastModified: new Date("2026-07-10T00:00:00.000Z"), | |
| changeFrequency: "weekly", | |
| priority: 0.9, | |
| }, | |
| { | |
| url: siteLinks.threads, | |
| lastModified: siteLastModified, | |
| changeFrequency: "weekly", | |
| priority: 0.9, | |
| }, |
| import { ThemeToggle } from "./theme-toggle"; | ||
|
|
||
| const NAV_LINKS = [ | ||
| { label: "Threads", href: "/threads" }, |
There was a problem hiding this comment.
The new "Threads" entry hardcodes the path as a string literal while every other
NAV_LINKS entry references a siteLinks property. If the /threads path is ever changed in site-config.ts, this entry won't be updated automatically. The footer has the same pattern — both should use siteLinks.threads.
| { label: "Threads", href: "/threads" }, | |
| { label: "Threads", href: siteLinks.threads }, |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| import { siteLinks } from "@/lib/site-config"; | ||
|
|
||
| const PRODUCT_LINKS = [ | ||
| { label: "useThread", href: "/threads" }, |
There was a problem hiding this comment.
Same hardcoded path issue as the navbar — and the label here is "useThread" while the navbar calls it "Threads". The two references to the same destination having different labels may confuse users who see one in the nav and the other in the footer. Aligning the label (and switching to
siteLinks.threads) keeps things consistent.
| { label: "useThread", href: "/threads" }, | |
| { label: "Threads", href: siteLinks.threads }, |
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d61eaa2c16
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| </div> | ||
| <a | ||
| className="inline-flex min-h-11 shrink-0 items-center gap-2 bg-primary px-5 font-medium text-primary-foreground text-sm transition-opacity hover:opacity-85" | ||
| href={`${siteLinks.github}/blob/main/packages/thread/README.md`} |
There was a problem hiding this comment.
Point the integration CTA at an existing guide
Every visitor clicking this CTA is sent to a GitHub 404: a repo-wide search of the reviewed commit shows packages/thread/ARCHITECTURE.md, but no packages/thread/README.md. Link to the architecture document or add the promised integration guide before publishing the page.
Useful? React with 👍 / 👎.
d61eaa2 to
07d3f1e
Compare
bf26771 to
e5bfc2d
Compare
e5bfc2d to
4f0419f
Compare
4f0419f to
4926a27
Compare
4926a27 to
4bb7a0f
Compare
4bb7a0f to
8b1a686
Compare
8b1a686 to
43a997e
Compare
Summary
useChatcompatibility.Behavior
Publishes a value-first product page for the package.
Verification
http://localhost:3052/threads.Screenshot
Review focus
Whether the page explains the AI SDK integration while keeping the playground primary.
Summary by cubic
Publish the Threads product page at
/threadswith a liveuseThreadplayground that staysuseChat-compatible. Adds navbar/footer links, full metadata, a sitemap entry, andsiteLinks.threadsfor discovery.New Features
/threadsmetadata (title, description, canonical, Open Graph).@ai-sdk/react➜@chatjs/thread/reactdiff, compatibility grid, architecture, CTAs to playground, package, and README.useThreadstate).Discovery
siteLinks.threadsand a product screenshot asset.Written for commit fc09bd1. Summary will update on new commits.
Stack