Update

[ildyria]

Summary by CodeRabbit

• New Features
  • Webshop integration now available with custom pricing, payment processing (Mollie and offline support), order administration, and download links management.
  • "Import via Web UI" feature is now generally available.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Two Astro pages were updated with content modifications. The pricing page gained a new "Webshop integration" feature with associated details including custom pricing, payment methods, and order management capabilities. The support page adjusted contributor counts, renamed one contributor, and reorganized team members between active and past contributors sections.

Changes

Cohort / File(s)	Summary
Supporter Edition Pricing Updates src/pages/get-supporter-edition.astro	Modified feature descriptions combining "Upload quota per user" and "User groups" into a single entry. Added "Webshop integration" feature with custom styling. Expanded specs list with new webshop-related entries (custom pricing, basket control, payment integrations, offline payments, order administration, download links). Removed isSoon flag from "Import via Web UI".
Support Page Team Restructuring src/pages/support.astro	Updated developer count from 6 to 4. Removed ppshobi and sancsin from active team, then relocated them to Past Contributors. Renamed RonnieTaz to cdzombak with updated avatar URL, alt text, and description changed from "reviewer" to "dev". Applied corresponding avatar/alt URL adjustments.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Content-driven changes with straightforward string/array modifications rather than complex logic
• Cohesive patterns within each file (similar types of edits repeated consistently)
• Primarily metadata and configuration updates requiring verification of accuracy rather than logic validation

Areas for attention:

• Verify accuracy of contributor information (names, URLs, descriptions) in support.astro
• Ensure "Webshop integration" feature details are complete and properly categorized in get-supporter-edition.astro
• Confirm isSoon flag removal from "Import via Web UI" is intentional

Poem

🐰 With webshops now integrated bright,
And team updates set just right,
New features bloom where commerce flows,
While past contributors take their bows—
The changelog hops to new heights! ✨

Pre-merge checks

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/pages/support.astro (1)

319-333: Fix malformed class attribute on translation block container

<div class=\max-w-3xl ...`>uses backticks without Astro/JS interpolation, which produces an invalid/unexpectedclass` value and a bunch of stray boolean attributes instead of Tailwind classes. This likely breaks styling of the translation section.

Recommend switching to a normal quoted class attribute:

-    <div class=`max-w-3xl mx-auto text-center p-6 rounded-md dark:shadow-none dark:border dark:border-slate-600`>
+    <div class="max-w-3xl mx-auto text-center p-6 rounded-md dark:shadow-none dark:border dark:border-slate-600">

🧹 Nitpick comments (2)

src/pages/support.astro (1)

82-123: Team member replacement looks consistent; consider handling historical entry explicitly

The switch to cdzombak (Chris Dzombak) with updated avatar, alt text, and role dev. is consistent with the rest of the team configuration. The commented‑out RonnieTaz block works as a temporary reminder, but long‑term it may be clearer either to remove it or to add that contributor explicitly to “Past Contributors” instead of keeping a commented object here.

src/pages/get-supporter-edition.astro (1)

104-111: Webshop integration pricing item wired correctly; optional clarity on availability

The new “Webshop integration.” item uses the same shape as existing entries (description, icon, classes.icon_bg / classes.icon), so it should render fine in Prices. Given the specs section marks Webshop integration as isSoon, you may optionally consider hinting at “coming soon” here as well (if it’s not yet live) to keep expectations aligned.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e44702b and 6ce553f.

📒 Files selected for processing (2)

• src/pages/get-supporter-edition.astro (3 hunks)
• src/pages/support.astro (3 hunks)

🔇 Additional comments (4)

src/pages/support.astro (2)

42-48: Stats widget update matches visible team composition

Devs count moved to 4, which aligns with the four active team entries below. No issues from a data or layout perspective.

---

302-315: Past contributors additions are coherent with previous team changes

Adding ppshobi and sancsin here as past contributors (with matching GitHub avatars and concise alt texts) cleanly reflects their move off the current team list. Data shape matches other items in the array.

src/pages/get-supporter-edition.astro (2)

81-87: Combined “User groups & upload quotas” wording is clear and consistent

Merging these into a single bullet better reflects the related functionality and still matches the detailed rows in the comparison table. No structural or syntax issues.

---

359-387: Webshop integration specs block is structurally sound and aligned with SE-only features

The new Webshop integration header (with isSoon: true) and its detailed rows (custom pricing, basket flow, Mollie, offline payments, order admin, download links) follow the existing pattern for feature sections: one header entry plus SE-only capabilities indicated via available: [false, true]. Data shapes match the rest of the specs array.