You're in the same boat like I am.
To people who are quick to downvote, hold your horse first and read before downvoting, this is coming from the guy who ACTUALLY try to do same thing above.
Trying to create DE/GUI is the closest definition of HELL as you can possibly face in Linux programming. Most of the codes are not documented and you are expected to go through all of the abstracted codes to figure out how the low level codes work in other GUI Toolkit or Desktop Environment. There is absolutely no reason for this hell to presist when developers should simply create documentations for their codes and EXPLAIN what the hell they're doing which is an extreme rarity in low level programming world in GTK, QT, and other projects like Wayland. Wayland literally only have a reference for you to go through, no explaination or reasoning as to how pieces in wayland go together and after my recent conversations with Wayland developers, they expected you to use WLC which is a bullshit way of saying that they won't document their shit and instead tell you to use an abstract library. Personally, I gave up with Wayland/X11 as many other have before me and went ahead with creating a new compositor/protocol which is quite frankly hell a lot easier to do than trying to deal with Wayland/X11 since you don't have to deal with abstract code and look over Arcan on how they did it and simply patch GTK/QT with custom platform to interface a custom display server which takes almost no effort at all.
To people thinking Wayland is a replacement for X11, it's not and it's worse than X11 (because X11 HAVE some documentations on the API) until they do documentations for Windows Manager, Compositor, Client Side GUI, and so go on for Wayland, I don't see Wayland becoming the norm happening. That is what expected of Wayland for any developer, we have to start somewhere and quite frankly, they just throw us the reference and expect us to know where the pieces go and that's bullshit.
Now you can start downvoting away and censor me to hell.
/rant