feat: add letscloud.io partnership

[zhravan]

Issue

Link to related issue(s):

---

Description

Short summary of what this PR changes or introduces.

---

Scope of Change

Select all applicable areas impacted by this PR:

• View (UI/UX)
• API
• CLI
• Infra / Deployment
• Docs
• Other (specify): ________

---

Screenshot / Video / GIF (if applicable)

Attach or embed screenshots, screen recordings, or GIFs demonstrating the feature or fix.

---

Related PRs (if any)

Link any related or dependent PRs across repos.

---

Additional Notes for Reviewers (optional)

Anything reviewers should know before testing or merging (e.g., environment variables, setup steps).

---

Developer Checklist

To be completed by the developer who raised the PR.

• Add valid/relevant title for the PR
• Self-review done
• Manual dev testing done
• No secrets exposed
• No merge conflicts
• Docs added/updated (if applicable)
• Removed debug prints / secrets / sensitive data
• Unit / Integration tests passing
• Follows all standards defined in Nixopus Docs

---

Reviewer Checklist

To be completed by the reviewer before merge.

• Peer review done
• No console.logs / fmt.prints left
• No secrets exposed
• If any DB migrations, migration changes are verified
• Verified release changes are production-ready

Summary by CodeRabbit

Release Notes

• New Features
  • Added Sponsors section to README featuring sponsor logos and links
  • Introduced "View All Sponsors & Partnerships" call-to-action button linking to dedicated sponsor page
  • New sponsor added and existing sponsor information updated with enhanced details

[coderabbitai]

Walkthrough

These changes enhance sponsor visibility across the documentation by adding a Sponsors section to the README with a two-column table, introducing a call-to-action button below the sponsor marquee, and updating the sponsors data file with a new sponsor entry and refined sponsor information.

Changes

Cohort / File(s)	Summary
Sponsors Documentation & UI README.md, docs/.vitepress/components/SponsorsMarquee.vue	Added Sponsors section to README with sponsor logos and links in a two-column table layout. Added a call-to-action button ("View All Sponsors & Partnerships") below the sponsor marquee with corresponding CSS styling for hover states, dark mode, and responsive adjustments.
Sponsors Data docs/public/sponsor/sponsors.json	Added new sponsor entry (Lets Cloud) with metadata fields. Enhanced HostUp entry with explicit type and contribution fields and description. Updated sponsor handle from "@Shravan20" to "@zhravan" with corresponding GitHub URL change.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Verify sponsor information accuracy and link validity
• Confirm CSS styling is responsive and consistent with existing design system
• Check that JSON data structure is valid and all fields are populated correctly

Possibly related PRs

• docs: readme redesign #400: Directly inverse—that PR removed the Sponsors section from README, while this PR adds it back with enhancements.

Suggested reviewers

• raghavyuva

Poem

🐰 A sponsors section now shines so bright,
With logos gleaming left and right,
A call-to-action leads the way,
New partners join us here to stay,
The rabbit hops with sponsor glee! ✨

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 title 'feat: add letscloud.io partnership' directly corresponds to the main changes: adding a new Lets Cloud sponsor entry, updating sponsor UI components, and introducing a CTA section for sponsors.
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 partnership-letscloud

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

README.md (1)

93-99: Sponsors section looks good; consider local assets and alt text tweaks

The new Sponsors block reads well and is consistent with the sponsor data. To harden it a bit:

• Consider hosting the logos in-repo (e.g., under docs/public/sponsor/ or assets/) instead of hotlinking gstatic/linkedin so README rendering isn’t dependent on third‑party CDNs or tokenized URLs.
• Optionally align alt text to the brand names (“Lets Cloud”, “HostUp”) for slightly better accessibility and screen‑reader output.

docs/.vitepress/components/SponsorsMarquee.vue (1)

39-43: CTA integration under marquee looks consistent; double‑check /sponsor/ target and states

The new “View All Sponsors & Partnerships” CTA fits nicely with the existing design, and the styling is consistent with the brand colors and responsive rules.

Two small things to verify:

• The /sponsor/ route (or page) is present and deployed in the docs site so this CTA doesn’t 404.
• You’re okay with the CTA showing even when sponsors are in loading/error state (since it’s outside the v-else block). If you want it hidden in those cases, it should move inside the successful‑load branch.

Also applies to: 359-404

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9f34c28 and 81ebe0a.

📒 Files selected for processing (3)

• README.md (1 hunks)
• docs/.vitepress/components/SponsorsMarquee.vue (2 hunks)
• docs/public/sponsor/sponsors.json (2 hunks)

🔇 Additional comments (1)

docs/public/sponsor/sponsors.json (1)

2-10: Sponsor data shape matches UI expectations; confirm copy and links with partners

The new Lets Cloud entry and the updated @zhravan record look structurally correct and compatible with the marquee component (name/avatar/type/website/github are all present and consistent).

Given this is outward‑facing partnership content, it’s worth double‑checking:

• The Lets Cloud offer text ($300 credit, 1‑click install, complimentary VPS) matches the actual agreed‑upon terms.
• The GitHub URLs (letscloud-community, zhravan) and websites are the ones the sponsors expect to be highlighted.

Also applies to: 20-25