- Issue created by @xjm
- 🇫🇷France nod_ Lille
just dumping the notes for now
attendees: lauriii, ben, sally, alex, dave, ckrina,
separate xb and core (repository) - different governance (user centered, more desingers) - how can people use it? unwillingness to have nodejs as dependency - no nodejs runtime dependency (define react as external) - changes in core, how to test xb for core changes? verify/test that we can extend xb in core - react validated - xb not in core repo, need governance - how is contrib going to extend react? (BC pretty good) - nodejs not required to install contrib modules - still nodejs not a runtime dependency xb scope - everyting in 'content' and 'struvture' - performance implications of having react required for doing all that - accessibility, how to be better that WP - to contribute => need to know react - contrib, field widgets? no need for react created field widget - contrib could provide a widget, but it's hard (json objectas render array, data types, component connected) - look into old admin-ui work for contrib widget definition - worry about make clicking to customize the admin very hard/impossible - concerned about limitting the options where customization needs to have a dev - @sally: ok to not have the same extensibility as we're used to - keep existing ui in case no-js is a requirement - Automatically closed - issue fixed for 2 weeks with no activity.