Documentation Review and Feedback

brianperry → credited cgreaten → .

brianperry → credited Warped → .

Some things that have come up so far:

* framework-agnostic vs framework agnostic
* Cross links on introduction page are broken (they don't account for the subdir we deploy to)
* It would be nice if things like our tabs worked if JS was disabled.
* for the sake of example vs. 'as an example', here's something you can try.

Another area is having a better path for newcomers (possibly newcomers to this type of js) to create a starting project to try the client. Our 'interactive playground' can serve this need, but the reader may not know about this until after the quick start. One thing that was proposed was adding a callout to the quick start that leads people to possible starting projects.

What starter projects should we have? Currently we have a React playground. Other options that seem like a high priority: vanilla js / Vite, HTML Only (no bundler), a meta framework (like Next). An progressively decoupled version in Drupal seems useful, but also hard to create.

When we have fleshed out the 'with frameworks' section more, we might be able to cross reference that to meet this need.

brianperry → credited kwiseman → .

We noticed that the Stackblitz interactive example only works in Chromium browsers.