Reusable components - How to model them

We have a large multi-lingual site which consists of content which is prepared centrally and then localised and locally produced content. We have over 40 different sites/languages with over 200 pages each (excluding product detail pages +2000). We are in the middle of rebuilding our setup as we are moving to react and didn't like our stack setup which wasn't correctly making use of branches.

We have some content heavy components like card overviews and carousels. How do we make these reusable across pages without our entries list becoming unmanageable? 

Do you use labels for content types or taxonomy? Without a folder structure it is really difficult to find content back in the entries list (despite the fairly good search functionality). 

0 replies

Be the first to reply!