“Spanned” tends to mean that a volume spans multiple disks. The trivial example is with LVM. A VG (volume group) has more than one PV (physical volume, a disk) and there is a LV (logical volume) in the VG. Part of the LV is in one disk and other part(s) on other disk(s).
The benefit of spanned volume is that you get larger volume. Say, two 4TB disks can host a 8TB volume.
The downside is that if any member disk breaks, then all data is lost. It might be possible to recover files that are entirely in one disk.
“Striped” spans too, but the writes are interleaved. (Not “first 4TB on A and second 4TB on B”.) Files smaller than stripe size are on one disk, but all bigger files are spread to both/all disks. The RAID 0 does stripe.
“Mirror”, for example RAID 1, writes everything to every disk. With those two 4TB disks you can get only 4TB volume, but data is redundant; every disk has full copy of data.
Can one set up in the interactive installer a VG that has multiple disks? I have no idea, but probably.
Single, large, “continuous” volume is convenient; you don’t need to consider what to put where. However, multiple separate volumes can be quite flexibly mounted to the tree; a “big disk” is not necessary if one can organize data.