Things should be working as outlined in the wiki: https://wiki.archlinux.org/index.php/Sy … managementIf you think it's important, you can add a line about halt, although it's already mentioned in systemd FAQ https://wiki.archlinux.org/index.php/Sy … r_stays_onThere's also https://wiki.archlinux.org/index.php/Al … o_ShutdownObviously you can use an alias e.g.alias halt='sudo sy
Network and Xorg issues sounds to me like you did too much in one go.https://wiki.archlinux.org/index.php/Be … leshootingCheck the connection, check the driver status and load the module: https://wiki.archlinux.org/index.php/Ne … figurationIf the network interface doesn't show up (eth0), read this part: https://wiki.archlinux.org/index.php/Ne … Interfaces
The ArchLinux Wiki has the best documentation available and with the problems you describe here, if it does not suffice, ArchLinux is likely not for you.Everyone can install ArchLinux and most can use it, but it does require more from the user than Ubuntu and such.https://wiki.archlinux.org/index.php/The_Arch_Wayhttps://wiki.archlinux.org/index.php/Beginners%27_Guide
Did you check the wiki on "Suspend to RAM"? It looks like there are a few tools there that should work for your needs.https://wiki.archlinux.org/index.php/SuspendAlso, after I switched to Awesome WM and didn't have the built in functionality to shutdown/reboot, I asked the same question and was lead to using Consolekit & dbus.
Running everything as root is a bad idea.I think you need to be in the "power" and "wheel" group in order to use shutdown and poweroff.Create a user and properly configure it's ~/.xinitrc to load a ConsoleKit session.