Let's separate installation from requirements.
The current hardware/install guides are a bit all over the place and conflate the two
Design:
Guides should be driven by the user's OS. This is the starting point for most people. Like "ok I have a windows with x cpu, and y gpus, what do i need"
Requirements guide should address dependencies, i.e. if users wanted to chck if they have proper deps. This is because we auto-install things now, we need to be transparent about what exact requirements are.
Suggested refactoring
Installation
Refactor Prerequisites section into Requirements pages.
Everything else, keep as is.
Requirements
Hardware Requirements
CPU, Disk, RAM, all that (in tabs)
Should cover stuff like:
cpu size, cpu skus, instruction sets
disk size, etc.
OS Requirements
Mac, Windows, LInux (in tabs)
Should cover stuff like:
os version
npm version, etc.
GPU Requirements
NVIDIA, AMD, Silicon, Snapdragon NPU, etc. (in tabs)
Let's separate
installation
fromrequirements
. The current hardware/install guides are a bit all over the place and conflate the twoDesign:
Guides should be driven by the user's OS. This is the starting point for most people. Like "ok I have a windows with x cpu, and y gpus, what do i need"
Requirements guide should address dependencies, i.e. if users wanted to chck if they have proper deps. This is because we auto-install things now, we need to be transparent about what exact requirements are.
Suggested refactoring
Installation
Refactor
Prerequisites
section into Requirements pages.Everything else, keep as is.
Requirements
Hardware Requirements
CPU, Disk, RAM, all that (in tabs)
Should cover stuff like:
OS Requirements
Mac, Windows, LInux (in tabs)
Should cover stuff like:
GPU Requirements
NVIDIA, AMD, Silicon, Snapdragon NPU, etc. (in tabs)
Should cover stuff like: