Per https://wikimedia.slack.com/archives/C08TB64J750/p1775043304314469 & eng enclave, let's settle on a clear structure for organizing our projects and any code they may share.
Proposal: standardize around a frontend directory structure & module names like this:
- resources/common -> ext.readerExperiments ^ shared components - resources/experiments/* -> ext.readerExperiments/* ^ individual experiments - resources/lib/* -> ext.readerExperiments/lib/* ^ external libraries
For shared/common resources, I would suggest to implement them in the relevant experiment first (although if we can make it somewhat generic from the go, all the better) and not move them into “common” until we have a 2nd experiment where they will actually be re-used (to prevent premature optimization when we can’t properly assess re-use nuances yet)