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

• New Features

  • Added a Sponsors section with logos and links in the README
  • Added a centered "View All Sponsors & Partnerships" call-to-action beneath the sponsor marquee (responsive and dark-mode friendly)

• Documentation / Content

  • Added a new sponsor entry and enhanced an existing sponsor’s details
  • Updated a sponsor handle and corresponding profile link

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

[coderabbitai]

Walkthrough

Added a Sponsors section to the README, appended a CTA button under the sponsor marquee component, and updated the sponsors JSON with a new sponsor, refined HostUp details, and a GitHub handle rename.

Changes

Cohort / File(s)	Summary
README update README.md	Inserted a Sponsors section containing a two-column Markdown table with sponsor logos and links, placed after About and before Contributors.
Sponsor marquee UI docs/.vitepress/components/SponsorsMarquee.vue	Added a centered "View All Sponsors & Partnerships" CTA below the marquee and related CSS (.sponsors-cta, .sponsor-details-link) including hover, dark-mode, and responsive rules.
Sponsors data docs/public/sponsor/sponsors.json	Added Lets Cloud sponsor entry; updated HostUp with explicit type, contribution, and description; renamed handle from @shravan20 → @zhravan and updated GitHub URL.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Validate JSON syntax and new/updated sponsor fields.
• Verify README table renders correctly in Markdown and links/images resolve.
• Review CSS changes in SponsorsMarquee.vue for visual regressions and dark-mode behavior.

Suggested reviewers

• raghavyuva

Poem

🐰 A tiny hop, a brand-new sign,
Logos lined up in tidy rhyme,
A button glows to call them near,
New names appear — the crowd's sincere,
I nibble code and celebrate with cheer! 🥕

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' accurately reflects the main changes in the PR, which include adding a new Lets Cloud sponsor entry to the sponsors.json file, updating related documentation, and adding UI components for sponsor management.
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

---

📜 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 81ebe0a and 3e15dae.

📒 Files selected for processing (1)

• README.md (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

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