Pi-holeDan

You might want to have a look at the OMV installation function (called as latest step of image creation): https://github.com/armbian/build/blob/master/scripts/customize-image.sh.template and discussion over there: http://forum.openmediavault.org/index.php/Thread/17855-Building-OMV-automatically-for-a-bunch-of-different-ARM-dev-boards/?pageNo=1
 
The idea behind was more or less a PoC to use Armbian's build system for other projects that rely on a Debian/Ubuntu base. I think you're looking into installation/integration in already running OS images. Since @Igoradded Pi-Hole installation already to Armbian's config tool I would think he has an idea what's missing or desirable?

Oh no! Please don't call /etc/network/interfaces normal, it's just one of many ways. For example on most of my boxes this file is empty in the meantime since all configuration is done in a more modern way with NetworkManager using profiles.

... and temperature readouts on older boards (A10/A20/A31) and mainline kernel (4.9.7+) is currently broken due to: 
https://forum.armbian.com/index.php?/topic/4178-cubietruck-soc-temperature-vanished/
It's planned to be fixed within upcoming update.

If there's /etc/armbian-release you can always rely on /etc/armbianmonitor/datasources/soctemp but still have to cope with the value either exceeding 1000 (millidegree) or not.
 
BTW: https://github.com/friendlyarm/linux/commit/d4940f17b1cd5dfded32c87d01bf7ac2cb1d26f7#commitcomment-21959223
 
Edit: If you don't want to rely on the existence of /etc/armbian-release this might help (tested and confirmed on +50 SBC with 2 kernel variants -- please keep that in mind that readouts differ based on device and kernel version)
 
https://github.com/armbian/build/blob/4c5504e48fcb853860e26f98218ab84891eea930/scripts/armhwinfo#L44-L77 https://github.com/armbian/build/blob/3e84ff3297543711c2f2974ba1bfacb0bfc818f0/scripts/update-motd.d/30-sysinfo#L35-L51

We have since made some changes to the temperature detection code to support more platforms and more approaches to get the information correct no matter what the SBC/OS Distro is. 
 
We stand behind our endeavor and will help out in any way we can.
 
As to the logo, it's now our trademark logo, but I completely understand a non Raspi user not wanting that image on their display! We are trying to get away from being thought of as just a Raspberry solution, but one that will work on many platforms, devices and virtual installations.