Parallel routes with @hero and @sidebar slots, can each one call fetchContent independently?

The two "slot" concepts are completely unrelated, which makes this simpler than it looks. Next.js parallel route slots are a routing construct; Croct slots are content placeholders. They compose without any special handling.

Each parallel segment is its own Server Component tree, so yes, each one can call fetchContent independently:

// app/@hero/page.tsximport {fetchContent} from '@croct/plug-next/server';
export default async function Hero() {    const content = await fetchContent('dashboard-hero', {        fallback: defaultHero,    });
    return <HeroSection {...content} />;}

Same pattern in @sidebar/page.tsx with its own Croct slot and its own fallback. The fetches run in parallel since the segments render independently.

The one rendering consequence to know: fetchContent reads the incoming request, which opts the route into dynamic rendering. And since parallel segments render as part of one route, a single personalized segment makes the whole route dynamic. For a dashboard that is usually what you want anyway, but it is worth knowing the static option is off the table once any segment personalizes.