Well, when it comes to Secure Boot, the official Arch documentation clearly states:

Note: Arch Linux installation images do not support Secure Boot. You will need to disable Secure Boot to boot the installation medium. If desired, Secure Boot can be set up after completing the installation.

On the topic of an Arch install, mostly it is the same as doing another distro-install but you do everything vai the GUI. However, there are a few extra steps. I highly recommend people to at least do the first install the manual way and this while making sure that you understand what you are doing. It simply helps to maintain your system with more ease when you have already seen certain steps in the install process. In my opinion the user needs to understand on a helicopterlevel what mounting is and how to do it, what chrooting is, how to work with Systemd (or another initsystem) and it helps too if the user knows which software is on his system and he can easily work with pacman via the terminal but the last won't be learned with an Arch-install, that will come with using the system. Also there is value in making (dumb) mistakes. I made a few myself when I was still learning the basics. My funniest and also a pretty dumb mistake is that 1 time I had no sound because I made the .config-directory as the root user. PulseAudio couldn't do its thing because the root owned the directory and even after fixing that PulseAudio won't start itself. A less dumb mistake, the first Arch install I didn't know that you needed to start up the init-service for NetworkManager. There is value in making such mistakes so just install Arch yourself and learn from it and you will get more at ease being your own systemadministrator. Currently I easily keep my Arch system running for many years without any issue other than an occasional broken package which I don't control. Though pacman is a great packagemanager we do get broken packages occasionally. For example, in 2024 we had a broken kernel (segfault while compiling dwm, many users had this), broken glibc (compiled without support for the older hashing method, it broke games) and there was a bug in the kernel caused by a little mistake from an AMD-developer (> vs >=) which made some games not start up, AMD did not find out about this bug until people reported the problem because ironically Resizable Bar camouflaged it on newer systems (Zen3/Zen4 + RDNA2/RDNA3).

Well, the main difference lies in the booting mechanism and partitioning scheme. You can use the master boot record (MBR) partitioning scheme and GRUB as a bootloader, installed directly on the disk's MBR.
Since most users and modern hardware rely on UEFI and the GPT partition table, I aimed to make the guide as relevant and helpful as possible for the widest audience.