When implementing SPI communication between a master and multiple slaves, there's basically two topologies to choose from: either resend the same data to each slave, or clocking data through all slaves in chain mode.
I have no idea what dark corner of the internet you got this from. The standard, most common, and obvious way to handle multiple SPI slaves is for each to have its own slave select line. That's precisely what they are for.
You wire the MOSI, SCK, and MISO lines all together, then each slave gets its own slave select line. The master asserts one of the slave selects at a time, and only that slave is allowed to drive the MISO line.
Same data to all slaves
In the special case of sending the same data to all slaves, you can tie all the slave selects together, or assert them all at the same time.
You do need to handle MISO differently however. Even if all the slaves are supposed to be identical, stuff happens and there could be a conflict. If you never care about returned data from any of the slaves, then you can just leave the individual MISO lines unconnected. Put a pulldown on the master's MISO input so that it is not floating.
Another option is to put pulldowns on all the MISO lines, then run them all into a wide OR gate, then the output of that into the master's MISO input. That allows normal bi-directional communication with individual slaves if you only assert one slave select, and 1 to N output only if you assert multiple slave selects. In that case you just ignore the received data in the master.