Marco
8c397c5dcb
Products now come from Payload's new "products" collection instead of a hardcoded catalog, same pattern already used for blog posts: - lib/payload.ts: getProducts()/getProductBySlug() (server-side fetch, 60s ISR) - New /api/products route so client components (CartContent, RelatedProducts) can reach the same data without a server-only import - lib/products.ts: useProducts() hook replacing the old PRODUCTS record - ProductGrid (/shop) fetches server-side directly; now shows all catalog products except notizbuch-klarheit (matches Figma's 4-card page-shop-overview — still cross-sold via RelatedProducts) - ProductSpotlight and /todo-cards' Pricing now pull price/photo from the same CMS product instead of a separately hardcoded "12,90 €", so the two can't silently drift apart - formatPrice moved to a new lib/format.ts (plain, no "use client") — Server Components can't call functions exported from a "use client" module directly, which lib/products.ts now is because of the hook Also fixes two unrelated bugs surfaced along the way: the add-to-cart button visibly resizing when its "Hinzugefügt ✓" success state showed (fixed with a CSS-grid text stack sized to the wider of the two strings), and removes the now-unused local product images from public/.
76 lines
3.0 KiB
TypeScript
76 lines
3.0 KiB
TypeScript
"use client";
|
|
|
|
import { useEffect, useRef, useState } from "react";
|
|
import { addToCart } from "../lib/cart";
|
|
import { useCartFly } from "./CartFly";
|
|
|
|
const FEEDBACK_MS = 2000;
|
|
const PRODUCT_ID = "todo-karten";
|
|
|
|
/**
|
|
* Shared by /todo-cards's Hero + pricing panel and Home's product
|
|
* spotlight. Used to navigate straight to /cart on click; now stays on the
|
|
* page instead (matching AddToCartInlineButton's behavior everywhere else)
|
|
* — adds to the cart, plays the fly-to-navbar-icon animation, and shows a
|
|
* brief inline success state instead of leaving the page.
|
|
*/
|
|
export function AddToCartButton({
|
|
label,
|
|
className,
|
|
}: {
|
|
label: string;
|
|
className?: string;
|
|
}) {
|
|
const [added, setAdded] = useState(false);
|
|
const timeoutRef = useRef<ReturnType<typeof setTimeout> | undefined>(undefined);
|
|
const buttonRef = useRef<HTMLButtonElement>(null);
|
|
const { fly } = useCartFly();
|
|
|
|
useEffect(() => () => clearTimeout(timeoutRef.current), []);
|
|
|
|
function handleClick() {
|
|
addToCart(PRODUCT_ID);
|
|
if (buttonRef.current) fly(buttonRef.current);
|
|
setAdded(true);
|
|
clearTimeout(timeoutRef.current);
|
|
timeoutRef.current = setTimeout(() => setAdded(false), FEEDBACK_MS);
|
|
}
|
|
|
|
const base =
|
|
className ??
|
|
"inline-flex items-center justify-center px-6 py-[0.8125rem] rounded-sm bg-brand hover:bg-brand-hover active:scale-[0.97] transition-all font-bold text-body text-text-primary whitespace-nowrap focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-brand focus-visible:ring-offset-2 focus-visible:ring-offset-bg-base";
|
|
// Trailing `!` — Tailwind v4's important-modifier syntax moved from a
|
|
// leading `!` to this trailing suffix — forces the success color to win
|
|
// over whatever bg-brand/text-text-primary each caller already baked
|
|
// into `base`, since appending on top can't rely on CSS source order
|
|
// the way branching a whole className (AddToCartInlineButton's
|
|
// approach) can when the base itself varies per caller.
|
|
const stateClasses = added ? "bg-success! hover:bg-success! text-white!" : "";
|
|
|
|
return (
|
|
<button
|
|
ref={buttonRef}
|
|
type="button"
|
|
onClick={handleClick}
|
|
className={`${base} ${stateClasses}`}
|
|
>
|
|
{/* CSS-grid text-stack, not just swapping the button's text node
|
|
directly — this button is inline-flex/content-sized (no w-full),
|
|
so "Hinzugefügt ✓" being shorter than most labels made the whole
|
|
button visibly shrink while showing the success state. Stacking
|
|
both possible texts in the same grid cell (both invisible ones
|
|
still contribute to sizing) reserves width for whichever is
|
|
wider, so the button's box never changes size either way. */}
|
|
<span className="relative grid">
|
|
<span className="invisible [grid-area:1/1]" aria-hidden="true">
|
|
{label}
|
|
</span>
|
|
<span className="invisible [grid-area:1/1]" aria-hidden="true">
|
|
Hinzugefügt ✓
|
|
</span>
|
|
<span className="[grid-area:1/1]">{added ? "Hinzugefügt ✓" : label}</span>
|
|
</span>
|
|
</button>
|
|
);
|
|
}
|