Skip to content

Add withdrawal form#171

Merged
SailReal merged 4 commits into
developfrom
feature/cancellation-form
Jun 18, 2026
Merged

Add withdrawal form#171
SailReal merged 4 commits into
developfrom
feature/cancellation-form

Conversation

@iammajid

Copy link
Copy Markdown
Contributor

Adds a withdrawal/cancellation form so customers can exercise their right of withdrawal, as legally required to be permanently and prominently accessible.

New /withdrawal/ page (EN/DE) modeled on the contact-sales form: posts
JSON to /connect/contact/withdrawal with name, email, po_number, product
(DESKTOP/ANDROID/IOS/HUB), optional reason, and altcha captcha.

Linked from the footer (Support) and as the first card in the /contact/
inquiries section.
@iammajid iammajid requested a review from overheadhunter June 18, 2026 12:54
@coderabbitai

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@SailReal, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 34 minutes and 59 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 118636a5-e27f-4420-b335-de73130dacac

📥 Commits

Reviewing files that changed from the base of the PR and between 3018ee6 and d899332.

📒 Files selected for processing (4)
  • content/contact/3-inquiries/1-withdrawal.de.md
  • content/contact/3-inquiries/1-withdrawal.en.md
  • i18n/de.yaml
  • i18n/en.yaml

Walkthrough

This PR adds a Withdrawal Form feature to the Cryptomator website. New bilingual (EN/DE) contact inquiry pages for "Right of Withdrawal" are inserted at weight=1 in the inquiries section, requiring existing press, enterprise, and jobs pages to have their weights incremented. New withdrawal page content files define page metadata with type: withdrawal. Bilingual i18n strings covering all form fields, placeholders, submit action, success messaging, and flow labels are added to both language files. A new Hugo layout template renders the form using Alpine.js and ApiForm, with captcha integration, validation feedback, and a success screen. A footer link to /withdrawal is also added.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • cryptomator/cryptomator.github.io#163: The new layouts/withdrawal/single.html instantiates ApiForm with a URL-based constructor, which directly aligns with the refactor of assets/js/apiform.js introduced in that PR.

Suggested reviewers

  • tobihagemann
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the primary change: adding a withdrawal form. It directly matches the main changeset objective.
Description check ✅ Passed The description is directly related to the changeset, explaining the purpose of the withdrawal form and its legal necessity. It provides meaningful context for the changes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/cancellation-form

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

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@layouts/withdrawal/single.html`:
- Around line 143-146: The resources referenced as $altchaJs and $altchaWorkerJs
are not being fingerprinted before accessing their integrity hashes, which
causes the integrity attribute to have no real value and silently breaks SRI
protection. Fingerprint each resource using the appropriate fingerprinting
method (such as .Fingerprint or similar) immediately after retrieving it with
resources.Get, before accessing the .Data.Integrity property for both the
altcha.js and worker.js script resources.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 387844ef-3f92-42f2-9eed-897620b5c37c

📥 Commits

Reviewing files that changed from the base of the PR and between fd42ebe and 3459e2c.

📒 Files selected for processing (14)
  • content/contact/3-inquiries/1-withdrawal.de.md
  • content/contact/3-inquiries/1-withdrawal.en.md
  • content/contact/3-inquiries/2-press.de.md
  • content/contact/3-inquiries/2-press.en.md
  • content/contact/3-inquiries/3-enterprise.de.md
  • content/contact/3-inquiries/3-enterprise.en.md
  • content/contact/3-inquiries/4-jobs.de.md
  • content/contact/3-inquiries/4-jobs.en.md
  • content/withdrawal.de.html
  • content/withdrawal.en.html
  • i18n/de.yaml
  • i18n/en.yaml
  • layouts/partials/footer.html
  • layouts/withdrawal/single.html

Comment thread layouts/withdrawal/single.html
@SailReal SailReal merged commit b08c219 into develop Jun 18, 2026
5 checks passed
@SailReal SailReal deleted the feature/cancellation-form branch June 18, 2026 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants