Skip to content

Conversation

@thedaviddias
Copy link
Owner

@thedaviddias thedaviddias commented Nov 15, 2025

This PR adds Reorient to the llms.txt hub.

Submitted by: plaza-quirk-paving

Website: https://reorient.guide
llms.txt: https://reorient.guide/llms.txt

Category: international


This PR was created via admin token for a user without GitHub repository access.

Please review and merge if appropriate.

Summary by CodeRabbit

  • Chores
    • Added new content entry for Reorient with metadata including website information, category classification, and publication details.

@vercel
Copy link

vercel bot commented Nov 15, 2025

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

Project Deployment Preview Comments Updated (UTC)
llms-txt-hub Ready Ready Preview Comment Nov 15, 2025 1:19pm

@coderabbitai
Copy link

coderabbitai bot commented Nov 15, 2025

Walkthrough

A new MDX file has been added to the content websites directory containing metadata and description for the "Reorient" entry. The file includes YAML front matter with standard fields (name, description, website, llmsUrl, llmsFullUrl, category, publishedAt) and a brief Markdown description body.

Changes

Cohort / File(s) Summary
New website content entry
packages/content/data/websites/reorient-llms-txt.mdx
Added new MDX file with YAML front matter (name, description, website, llmsUrl, llmsFullUrl, category, publishedAt: '2025-11-15') and Markdown description body for Reorient entry.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • Simple single-file addition with static metadata content
  • Review focuses on verifying front matter correctness and content accuracy

Possibly related PRs

  • PR #262: Adds new MDX metadata entry for LLMs in the content/websites directory with identical front matter structure.
  • PR #286: Adds new website MDX content files using the same front-matter schema and organizational pattern.
  • PR #283: Adds new llms.txt MDX data files to the websites content area, following the same hub entry pattern.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title clearly and concisely summarizes the main change: adding Reorient to the llms.txt hub, which directly matches the file addition and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch submit-reorient-1763212547857

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 935e684 and 9a37e8e.

📒 Files selected for processing (1)
  • packages/content/data/websites/reorient-llms-txt.mdx (1 hunks)
🧰 Additional context used
🔍 Remote MCP

I'll search for additional context to help review this PR about adding Reorient to the llms.txt hub.## Summary of Relevant Context for PR #460 Review

llms.txt Standard & Hub Requirements

The llms.txt hub is a popular open-source hub tracking websites implementing the llms.txt standard, with a comprehensive directory allowing developers to discover implementations, study how organizations structure their files, and access tools for implementation.

For submissions to the hub, websites must have implemented llms.txt on their site before submitting via the submission process on the homepage. Submissions require the website URL, title, category, description, and contact email, with most reviewed within 24-48 hours after verifying the llms.txt file is accessible and meets quality standards.

llms.txt File Specification

The llms.txt file spec requires files be located at the root path /llms.txt of a website, with a markdown structure containing an H1 title (the only required section), a blockquote summary with key information, and zero or more detailed markdown sections.

Files should be kept under 2,000 tokens (roughly 1,500 words) for optimal AI processing, with longer content placed in llms-full.txt.

Hub Categories & Data Structure

Projects are organized into primary categories (AI & ML, Developer Tools, Data & Analytics, Integration & Automation, Infrastructure & Cloud, Security & Identity) and secondary categories (personal, agency, e-commerce, education, media, international, other). The PR categorizes Reorient as "international," which aligns with the hub's established categorization system.

Key Verification Points for Review

Before merging, confirm:

  1. The submission system automatically monitors llms.txt files and updates token counts
  2. The Reorient website (https://reorient.guide) actually has a valid, accessible llms.txt file at the root path
  3. The MDX front matter fields match the hub's expected metadata schema (name, description, website, llmsUrl, llmsFullUrl, category, publishedAt)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Validate
🔇 Additional comments (3)
packages/content/data/websites/reorient-llms-txt.mdx (3)

6-6: Clarify the empty llmsFullUrl field.

The llmsFullUrl field is empty. Per the llms.txt specification, longer content should be placed in a separate llms-full.txt file. Please confirm whether this field should be populated with a URL (e.g., https://reorient.guide/llms-full.txt) or if keeping it empty is intentional given the content is brief.


11-13: Markdown content is well-formatted and consistent.

The Markdown title and description align with the front matter metadata. The content is clear and appropriate for the hub.


1-9: llms.txt file verified as accessible — ready to merge.

The llms.txt file at https://reorient.guide/llms.txt is accessible and returns valid content with site description, links, and structure. The MDX file structure is correct with all required metadata fields properly populated.


Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants