feat: add DC Hub to llms.txt hub

[thedaviddias]

This PR adds DC Hub to the llms.txt hub.

Submitted by: jonathan

Website: https://www.dchub.cloud
llms.txt: https://www.dchub.cloud/llms.txt
llms-full.txt: https://www.dchub.cloud/llms-full.txt
Category: data-analytics

---

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

Please review and merge if appropriate.

Summary by CodeRabbit

• Documentation
  • Added a new DC Hub resource page with description and reference links.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
llms-txt-hub	Ready	Preview, Comment	Feb 1, 2026 10:46am

[coderabbitai]

Walkthrough

A new MDX content file for the DC Hub website has been added to the websites data directory with metadata fields and a description.

Changes

Cohort / File(s)	Summary
Website Content packages/content/data/websites/dc-hub-llms-txt.mdx	New MDX page with YAML front matter (name, description, website, llmsUrl, llmsFullUrl, category, publishedAt) and DC Hub description content

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• #397 — Adds new .mdx dataset files under packages/content/data/websites with identical front-matter schema for website entries
• #283 — Adds new llms-txt MDX data files in the content websites folder with equivalent metadata structure
• #387 — Adds new MDX website entry files under packages/content/data/websites following the same llms-txt hub schema

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: adding DC Hub to the llms.txt hub. It is concise, specific, and directly matches the changeset content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch submit-dc-hub-1769942571267

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[sentry]

Bug: The publishedAt field for the new DC Hub entry is set to a future date (2026-02-01), which will cause it to be incorrectly pinned to the top of date-sorted lists.
_{Severity: MEDIUM}

Suggested Fix

Change the publishedAt date in dc-hub-llms-txt.mdx from '2026-02-01' to a date in the past, likely the actual publication date. Based on the commit timestamp, '2025-02-01' would be a reasonable value. Consider adding validation to the content schema to prevent future dates in the publishedAt field.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: packages/content/data/websites/dc-hub-llms-txt.mdx#L8

Potential issue: The new DC Hub website entry in `dc-hub-llms-txt.mdx` has its
`publishedAt` field set to `'2026-02-01'`, a date in the future. Since content like the
"Recently Added" section is sorted by `publishedAt` in descending order, this entry will
be incorrectly displayed as the most recent item until February 2026. This gives it
undeserved prominence over genuinely newer entries and misrepresents its publication
date. The schema for this field does not validate against future dates, allowing this
issue to affect production display logic.

_{Did we get this right? 👍 / 👎 to inform future reviews.}