Installation page refinements

szarnyasg commented 4 months ago

[ ] The sections stating Currently not available should be removed. This will reveals some bugs in the selection mechanism, these should be fixed.
[ ] The page should detect the CPU type. This applies both to the landing page (e.g. for the Linux CLI client) and to the detailed installation page.
[ ] Add Wasm to the detailed installation page.
[ ] The installation page currently has a query string but if the link is opened, the query string has no effect: the site jumps back to the default auto-detected view (e.g. macOS + CLI + stable).

ned2 commented 3 months ago

hey @szarnyasg something else perhaps to consider: when the Package manager option is selected for both Windows and macOS the provided Usage example still indicates the path ./duckdb rather than the bare executable duckdb which respective package manager should have added to the user's PATH. (have tested that works as expected with brew on macOS but not winget on Windows)

szarnyasg commented 3 months ago

Good point, thanks! We'll work this into the installation page.

duckdb / duckdb-web

Installation page refinements #2372