One data repo for all content libraries; presets get a browse option, not a rewrite
· 4 min read
The question: every new content library (page-builder templates, then component presets, then icon packs) was about to get its own GitHub data repo. That felt messy. Can we put all library content in one repo — and if so, what actually has to stay split?
