Not sure about the exact phrasing but I think something like this would be nice. It'd be overwhelming to list every module that touches the DOM, but it may be frustratingly vague to just say "most don't, some do". Is there a general principle by which the uninitiated reader might spot which do and don't? As a beginner programmer learning D3 I know I didn't have a good mental model of where the DOM fit in, but I think I'd at least be able to spot "does this take a selection".
* checkpoint vitepress docs
* edits
* edits
* hero drop shadow
* d3-array edits
* resolve d3
* split d3-array
* move d3-array stuff around
* d3-array is collapsed: true
* italicize parameter names
* searching edits
* update dependencies
* d3-array edits
* array edits
* array edits
* array edits
* array edits
* array edits
* move files
* array edits
* array edits
* array edits
* getting started edits
* modules page
* array edits
* more structure
* live example
* dsv edits
* fetch edits
* dsv edits
* random edits
* time format edits
* time edits
* time edits
* modules edits
* color edits
* color edits
* interpolate edits
* scale-chromatic edits
* selection edits
* break up d3-interpolate
* scale edits
* time scale edits
* scale edits
* scale edits
* band edits
* band edits
* more descriptive titles
* band and point edits
* sequential edits
* diverging edits
* quantize edits
* quantile edits
* threshold edits
* doc edits
* fix titles
* sequential edits
* axis edits
* axis edits
* axis edits
* shape edits
* shape edits
* dark mode chart
* dark mode chart
* curve edits
* interpolate edits
* line edits
* link edits
* radial edits
* pie edits
* symbol edits
* stack edits
* stack examples
* path edits
* polygon edits
* quadtree edits
* random examples
* ease edits
* ease edits
* ease edits
* timer edits
* delaunay edits
* quadtree find example
* voronoi edits
* dispatch edits
* contour edits
* chord edits
* chord edits
* fix find highlight
* quadtree animation
* transition edits
* transition edits
* transition edits
* zoom edits
* drag edits
* brush edits
* force edits
* voronoi neighbors example
* hierarchy edits
* api edits
* community edits
* getting started edits
* geo edits
* Add short "D3 in React" section (#3659)
* Add short "D3 in React" section
I know you removed the TODO but I was already trying to fill it in! I think just making the distinction of modules that touch the DOM and those that don't was super clarifying for me personally when I figured that out. And I always forget the most basic ref pattern (and still might've messed it up here). I don't think we should get into updating or interactivity or whatever, but I think just this much goes a long way toward demystifying (and showing just the most basic best practices).
* forgot i made data generic, rm reference to normal distribution
* useEffect cleans up after itself
Co-authored-by: Mike Bostock <mbostock@gmail.com>
* Update getting-started.md
---------
Co-authored-by: Mike Bostock <mbostock@gmail.com>
* build fixes
* index edits
---------
Co-authored-by: Toph Tucker <tophtucker@gmail.com>
