adhikareeprayush / adhikareeprayush/slide-forge

Wire custom community Slide.tsx renderers at runtime

未關閉
#26 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
feature help wanted layouts sdk
主要語言
TypeScript
星號
0
分支
3
PR 合併指標
30 天內沒有已合併 PR

描述

## Summary
SDK scaffold creates `Slide.tsx` per layout, but runtime always uses `SlideCanvas` from `@slideforge/ui`.

## Tasks
- [ ] Load optional `Slide.tsx` from `community//` at API startup or on demand
- [ ] Fallback to `SlideCanvas` when no custom renderer
- [ ] Document when custom renderers are appropriate vs slot-only layouts
- [ ] Preview command uses same loader

## Files
- `packages/ui/src/SlideCanvas.tsx`
- `apps/api/src/services/layout-registry.ts`
- `packages/sdk/src/preview.ts`
- `community/README.md`

貢獻指南

開啟貢獻指南

研究方向

Read apps/api/src/services/layout-registry.ts first, then compare packages/sdk/src/preview.ts with packages/ui/src/SlideCanvas.tsx to understand the current rendering path. Done means optional community//Slide.tsx renderers load at API startup or on demand, missing renderers fall back to SlideCanvas, the preview command uses the same loader, and community/README.md documents when custom renderers are appropriate.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
typescript
領域
api, developer-experience, documentation, frontend
Issue 類型
功能
難度
4/5
預估耗時
3-5 天
活躍度
冷清
描述清晰度
基本清楚
新手友好度
52/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。