chore(docs): update support sections

[s0up4200]

• Direct users to GitHub Discussions for feature requests and bug reports
• Clarify GitHub Issues is for work in progress
• Remove duplicate instructions

Summary by CodeRabbit

• Documentation
  • Reworked support guidance to combine Discussions and Issues and add a “Support Development” section.
  • Added a detailed license key flow: donation → confirmation → 100% discount code → license entry (lifetime).
  • Introduced “Donation Methods” with sponsor/coffee options for two maintainers and explicit cryptocurrency donation options (BTC, ETH, LTC, XMR).
  • Clarified that donations unlock premium themes and added Discord contact and thank-you note.

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

[coderabbitai]

Walkthrough

Documentation replaces "pay what you want" language with "donate what you want", adds GitHub Discussions/Issues for support, documents a License Key donation flow, and lists multiple donation methods including GitHub Sponsors, Buy Me a Coffee, and explicit cryptocurrency addresses for two contributors.

Changes

Cohort / File(s)

Summary

Documentation Updates README.md, documentation/docs/support.md

Rework support section: switch payment wording to donation wording; add GitHub Discussions (feature requests) and GitHub Issues (work in progress); add "Support Development" note; document License Key flow (donation → Discord DM → transaction hash → 100% discount code → Polar link → license entry → lifetime key); add "Donation Methods" with GitHub Sponsors and Buy Me a Coffee links for soup and zze0s; add "Cryptocurrency" subsection with BTC, ETH, LTC, XMR addresses for both contributors; update closing notes and Discord contact instructions.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

• docs(funding): add donation methods and crypto addresses #583: Adds/expands donation methods and cryptocurrency funding details in README/docs.
• feat(ui): unify payment options into single dialog #864: Updates license/payment/support flow and related README/support documentation (donation flow, crypto, Discord/Polar references).
• docs(README): add Buy Me a Coffee link #863: Adds Buy Me a Coffee donation links and updates support/donation content for zze0s.

Suggested reviewers

• zze0s

Poem

🐇 In the burrow I nibble, a thank-you in code,
Coins and coffees arrive down the road,
Keys bloom like carrots from generous ground,
Discussions and issues now gather around,
Hoppy thanks — your support keeps us bold! 🥕

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 'chore(docs): update support sections' directly aligns with the main changeset, which updates README.md and documentation/docs/support.md to restructure support information.
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 docs/update-support-sections

---

📜 Recent review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5de6752 and 99cb31e.

📒 Files selected for processing (2)

• README.md
• documentation/docs/support.md

🔇 Additional comments (7)

README.md (4)

57-58: ✅ Support channels clearly documented.

GitHub Discussions and Issues provide distinct, appropriate channels for feature requests, bug reports, and work in progress. Good organization.

---

60-73: ✅ License Key flow is well-documented.

The step-by-step donation → discount code → Polar redemption → license key flow is clear, actionable, and establishes the voluntary support model effectively.

---

84-101: ✅ Cryptocurrency addresses clearly attributed and well-formatted.

BTC, ETH, LTC, and XMR addresses for both contributors are explicit, properly labeled, and appear syntactically correct. Users can easily identify which address to use.

---

102-106: ✅ Closing messaging is supportive and actionable.

Clear statement that all methods unlock premium themes, with a fallback Discord channel for questions. Reinforces the voluntary support model with gratitude.

documentation/docs/support.md (3)

14-21: ✅ License Key flow updated with consistent terminology.

Terminology shift from "Pay what you want" to "Donate what you want" aligns with PR objectives. The flow remains clear and actionable.

---

32-52: ✅ Cryptocurrency section with copyable addresses is user-friendly.

CopyAddress component provides excellent UX for crypto addresses. All four currencies (BTC, ETH, LTC, XMR) are clearly labeled by contributor and appear syntactically correct. Good practice to include multiple address types.

---

56-56: ✅ Closing message updated for terminology consistency.

Reference to "donation methods" is consistent throughout the document and reinforces the voluntary support model.

---

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

[github-actions]

PR Review Summary

Reviewed areas: Documentation

Passed Checks

• Documentation: Changes successfully synchronize README.md with the documentation site
• Consistency: Content in README.md now matches documentation/docs/support.md
• Clarity: Improved guidance directing users to GitHub Discussions for feature requests/bug reports
• Terminology: Consistent use of "donate" instead of "pay" throughout

Observations

This PR improves the user experience by:

1. Clearer support channel guidance - Users now know to use GitHub Discussions for feature requests and bug reports, while Issues are for active work (README.md:57-58)
2. Better onboarding - The donation process and license key redemption flow is now visible in the README, making it easier for new users to support the project
3. Content synchronization - README.md now mirrors the support documentation, reducing maintenance burden and confusion

Recommendations

✅ No issues found - this is a clean documentation update that improves clarity and consistency.

Areas Skipped

• Security: Not applicable (documentation only)
• Performance: Not applicable (documentation only)
• Frontend: Not applicable (documentation only)
• Integration: Not applicable (documentation only)

---

Automated review by Claude Code

[coderabbitai]

Actionable comments posted: 2

♻️ Duplicate comments (1)

documentation/docs/support.md (1)

16-16: Fix the maintainer name inconsistency (duplicate of README issue).

Line 16 refers to "ze0s" but lines 29-30 list "zze0s" with the corresponding donation links. This same inconsistency appears in README.md. Ensure the correct spelling is used consistently in both files so users can find the correct maintainer on Discord.

Also applies to: 29-30

🧹 Nitpick comments (2)

README.md (1)

66-73: Clarify the license key procurement flow for new users.

The License Key section is comprehensive, but consider whether the flow is intuitive enough for first-time users. The sequence involves: donation → Discord DM → discount code → Polar redemption → license key entry. Consider adding a brief note that explains this is a semi-manual process (by design) to prevent fraud while maintaining ease of access.

Alternatively, add a "Questions?" section that addresses common confusion points (e.g., where exactly to redeem on Polar, what "100% discount code" means, whether multiple licenses are supported per instance).

documentation/docs/support.md (1)

32-52: Excellent use of the CopyAddress component for cryptocurrency donations.

The custom component provides a better user experience compared to the plain text listings in README.md. Users can easily copy addresses with a single click rather than manually selecting and copying. This reduces transcription errors when donating cryptocurrency.

Consider applying the same component-based approach to README.md for consistency and improved UX across documentation, or document why the two formats differ (if intentional).

📜 Review details

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 04f361a and 5de6752.

📒 Files selected for processing (2)

• README.md
• documentation/docs/support.md

⏰ 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: review

[netlify]

✅ Deploy Preview for getqui ready!

Name	Link
🔨 Latest commit	99cb31e
🔍 Latest deploy log	https://app.netlify.com/projects/getqui/deploys/695938f7a28c380008cd758e
😎 Deploy Preview	https://deploy-preview-1063--getqui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.