Lots of advice given so far, and here's another bit...
My system has been in place for a loooong time so has evolved rather than been designed from scratch. I am still using four analog cameras, and additionally have several IP cameras. I prefer analog because of the immediacy (no lag - IP cameras can lag by a LOT) and better degradation. If the signal goes bad (poor wiring or something) the resolution turns pants but you still have usable video. With IP it's just a stuttering mess of blocks. But analog is not high resolution.
If I were starting again I would first sort out the NVR - cameras are many and varied and easily acquired, but the NVR determines what you can do with your system. I've tried a few PC-based and standalone boxes (and designed a commercial system) and my first choice now would be a Dahua of some kind. The main reason for that is the motion detection, which isn''t just motion detection but recognises people, vehicles, etc. But the magic part is that you can set traps and trigger when an object crosses the trap (this way, that way, both ways). So, for instance, looking at our drive there is a bunch of moving vegatation and a road with passing traffic. The trigger is a line drawn across the top of the drive and it only triggers is something crosses that (to come up the drive). Everything else is ignored. There is also a box drawn around the car and that triggers when the car either disappears or arrives - it's not movement per se but something appearing or disappearing within the box. As a result, it captures everything it should and nothing it shouldn't. Simples. I presume other manufacturers may have similar features.
Having got that sorted, the next thing is cameras. IP is the rage nowadays, but check that your NVR will use the desired features with the cameras. For instance, the great triggering on the Dahua only works with analog inputs (on this model) and relies on IP cameras doing their own alert stuff and letting the NVR know about it. Not sure why that is, but could be related to compression and throughput. Analog signals have many chips available to process them whereas digital cameras get the software treatment.
IP cameras or whatever flavour should have ONVIF connectivity, and then they will talk to just about anything. Ones that don't allow that are often either vendor-locked or require a cloud connection (or, more likely, both) so don't buy one that doesn't do it. IME, even if a camera looks a bit so-so, if it does ONVIF you can ignore all the built-in rubbish and just stream that.
POE is worth keeping in mind for simplicity of cabling, but it can get expensive real fast to use only gigabit POE switches. Most cheaper cameras would need a POE adapter to 12V too, so if they're close to a power point that can be simpler. It's also worth arranging things so all your IP cameras are on a separate physical subnet to your computer LAN - with them streaming 24/7 that's a fair amount of bandwith your pron downloads could use. In practice, that might just mean having all the feeds arrive in the same switch that the NVR is on (as opposed to traversing several switches to get there) since the switch can deal with port-to-port routing.
WiFi, as already noted, isn't good for security, but don't discount it out of hand. Sometimes you can get power to some location but data (or video) is a showstopper. Currently we have a WiFi camera out back watching out for foxes approaching the electric fence, and it works pretty good. Surprisingly good, actually, but if I could get a CAT5 (we're not fussy) out there I would do that instead. But needs must and all that - something is often better than nothing.