website: Update whatsnew

[felixpalmer]

For #9172, preview the changes here: https://felixpalmer.github.io/deck.gl/docs/whats-new

I've done a review of what new features are in master in the codebase & the docs. I've cross-referenced who is responsible for each change, could you check you're happy with the added text:

@ibgreen-openai widgets, core async picker, View.clone, WebGPU layers
@chrisgervang Multi-view support, widget theming, pydeck integration

There are a few docs pages missing still, these can be added in follow up PRs

Change List

• Fix broken anchors & misc website build errors
• Update whatsnew

[coveralls]

coverage: 91.104% (+0.009%) from 91.095%
when pulling 2978c5c on felix/9.2-whatsnew
into 75dd4f3 on master.

[ibgreen]

• Some of these are less mature / more experimental and it was kind of semi-intentional that they were omitted here.
• It might be worth going through widgets/index.ts and review what should be exported with underscore and what should not.

[felixpalmer]

OK, so for the whatsnew, should we remove the 4 that don't have any docs?

[felixpalmer]

As for marking experimental/exporting with underscore - I feel the widgets are all pretty self-contained, so there is not so much harm done removing the underscore, we save users from a future breaking change that way.

[ibgreen-openai]

is not so much harm done removing the underscore, we save users from a future breaking change that way.

OK sure. This is how I thought about it:

• To me, the underscore signals that these are not fully audited and ready, and may change.
• a downside if we remove the underscore and then change the widget props is that we may break user code with less warning...

Generally we have a higher bar for experimental code in deck.gl, but since widgets is a new area I felt it was OK to be more experimental.

My alternative was to put the underscore widgets in @deck.gl-community/widgets, while that would keep deck widgets to a higher bar, it would also slow down experimentation and adoption a little.

[chrisgervang]

It'd be relatively little effort to add the 4 missing docs.

The thinking too is we can make breaking changes to props in a minor release on experimental components, or even remove/combine/split-apart widgets.

I'd prefer to keep the underscore, or just clearly denote they're experimental in some other way

[ibgreen-openai]

If we are going through the trouble of listing all widgets, should we also list webgpu ready layers?
And maybe add a WebGPU badge to their doc pages?

[ibgreen-openai]

Suggested change

	- Async DeckPicker methods - New asynchronous methods for improved picking performance and non-blocking operations
	- Async DeckPicker methods - New asynchronous methods for non-blocking operations and (depending on platform and usage) improved picking performance.