feat: add Clouve to llms.txt hub

[thedaviddias]

This PR adds Clouve to the llms.txt hub.

Submitted by: aj

Website: https://www.clouve.com
llms.txt: https://www.clouve.com/llms.txt
llms-full.txt: https://www.clouve.com/llms-full.txt
Category: infrastructure-cloud

---

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

Please review and merge if appropriate.

Summary by CodeRabbit

• New Features
  • Added a new website entry: Clouve. Includes name, description, category (infrastructure-cloud), and publish date. Provides links to the site and its LLMs configuration files (llms.txt and llms-full.txt) for improved discoverability.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
llms-txt-hub	Ready	Preview	Comment	Sep 4, 2025 2:24pm

[coderabbitai]

Walkthrough

Adds a new MDX content entry for the website “Clouve,” including YAML front matter (name, description, website, llmsUrl, llmsFullUrl, category, publishedAt) and a simple H1 body. No other files are modified.

Changes

Cohort / File(s)	Summary
Content: new website entry packages/content/data/websites/clouve-llms-txt.mdx	Added MDX file with front matter (name, description, website, llmsUrl, llmsFullUrl, category, publishedAt) and an H1 matching the site name plus description in body.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Add deliverect-llms-txt.mdx to the directory #343 — Adds a similarly structured MDX website metadata entry with the same front-matter keys and simple body layout.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch submit-clouve-1756995695831

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

packages/content/data/websites/clouve-llms-txt.mdx (1)

11-13: Avoid duplicate H1; the page title is likely rendered from front matter.

If the site template already uses name as the H1, drop the in-body # Clouve to prevent double titles. Keep just the description paragraph.

-# Clouve
-
 Clouve connects businesses with enterprise-ready applications while empowering developers to monetize their solutions through our secure platform.

If you confirm the template behavior, I can push the minimal edit.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 966c32c and 91015d9.

📒 Files selected for processing (1)

• packages/content/data/websites/clouve-llms-txt.mdx (1 hunks)

🧰 Additional context used

🪛 LanguageTool

packages/content/data/websites/clouve-llms-txt.mdx

[grammar] ~11-~11: Ensure spelling is correct
Context: ...cloud' publishedAt: '2025-09-04' --- # Clouve Clouve connects businesses with enterpri...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (1)

packages/content/data/websites/clouve-llms-txt.mdx (1)

1-9: Approve front matter Verified that https://www.clouve.com and both llms endpoints return HTTP 200 with correct content types (text/plain for .txt) and that infrastructure-cloud is an allowed category.