Devuan deliberately keep things simple and generic. This is for you to build upon, make it easy to roll your own free software distribution tailored to your and your users needs and preferences.
There are several ways you can achieve your goal:
Forking Devuan is the heavy-weight option: you take care of everything and don't care about compatibility. But well, we did it to Debian, right? It's free software, if you don't like it, fork it. If you love it, fork it too (and contribute back your changes)!
Using Devuan Blends to create a meta-package that pulls in all your favorite software. It's like a fork, except you keep everything within the Devuan repositories, so it's much easier to maintain, and you benefit from Devuan's infrastructure.
Rolling out your own Devuan derivative distribution is recommended in the case you want to make changes that are incompatible with the main archive. For example, you want a rolling release, or compiling a mix of
unstable to keep on the edge of some specific set of software.
Discuss the pros and cons of each strategy for your own case, and share your experience for others to try and know the caveats.