Don't get stuck.
For all open-source CMS platforms or portals, there may be some preferred ways of doing things. Some libraries and methods may even be "invented" by the developers of these platforms in attempt to minimize integration and optimization issues. This all makes sense from a logical standpoint and, if you're comfortable with it, you should abide by that.
However, for whatever reason (be it lack of documentation, lack of developer or community examples, incomplete code, or simply the frustration of learning something completely new), it wouldn't be open source if it didn't allow you to do your own thing and use your own sources.
It's open-source... it should work.
Don't just do it to be stubborn.
On the other side of that spectrum, you may want to at least give it a try before you completely ditch it. There are still many reasons why the suggested method may give you some benefit.
Probably the most important and obvious reason is that you're going to be adding another method, possibly on top of the existing one. There can be an impact to load-times and the new functionality might clash with existing functionality.
Another big reason is consistency. The team you're working with may already have a method in place and to change the way you do something on your specific project may not make sense from that standpoint. Besides that, there may already be code already built upon that method from the rest of the team that you can reuse.
There's also the potential that you might learn something new and excited.
Do it for the team.
Just keep this in mind when you're struggling with something. I know how one can get stuck on something, driving them into a paradox with the frustration of constantly trying something different to get something to work properly. If you start spinning your wheels too much, suggest a change to the team and provide a valid use-case where a new method would help you. Use this article for validation if you need to.