It has taken a considerable sum of money, upfront, to invest in our podcasting equipment, and podcasting hosting. And that doesn't even begin to scratch the surface on the number of upfront hours co-host Zach has spent on the design and development of our website.
For us, this is a passion project and maybe, eventually down the line, a side-hustle of sorts. However, it is our ultimate goal to keep the core podcasts absolutely free-of-charge. We don't believe in garden/pay-walling in order to access our content. It is never our expectation to make money off of our art, but rather to let others enjoy it freely. Although, with that being said, if you do enjoy our content and want to help support the continuation of future episodes as well as increase the chances of them being aired more frequently, you are more than welcome to contribute monetarily, design, coding, volunteering, offering your expertise as "expert" on our podcast. We are happy when our random act of kindness is reciprocated in unexpected ways. After all, it's good karma, all-around.
Regarding the former point, while we could attempt to monetize our podcast by including generic ads, or focusing heavily on making a buck, doing so would be aimless, reckless and would certainly alienate a cross-section of our audience/listening demographic? Why? Because we are a different kind of podcast, with a very different philosophy of what we offer to the aether. It is important, just like the origins of organic food, that it comes from a place of goodness. Therefore, if we do accept donations, it will either be individual donations, either through a donation platform with low percentage cuts, through patreon, or contributed in other ways.
We appreciate hearing from and offers from other trades, experts, craftsmen/artists/artisans, or even people like and/or that can relate to us. As experts in your respective realm, you are the master and you could potentially help elevate waht we've created. However, in doing so, it is important that we emphasize this doesn't mean any ownership over the site or the podcast and inviting this sort of help, we are in no way beholden to you monetarily, nor emotionally. However, we will credit you for your work and also consider affliating with you, which if this show ever becomes popular, would be a great way of showcasing your talents and driving business to your livelihood. It can be potentially, win-win.
If you are passionate and you love what you hear and want to help shape the future of it, to both look and sound better, we are open to hearing from you. I have created online communities before and there is nothing quite like surrounding yourself around people of like mind and like passions. It is an opportunity for magic to happen, as great minds think alike and when we combine our minds together, we can move mountains - or make the impossible, possible!
Next, you might be wondering: who's help would we automatically consider, even through careful review and ignoring the entirely unnecessary "cold-call" internet marketeers? I'm glad you asked! We can use your help currently on three main fronts:
One proposed project would be to create a fully object-oriented and intuitively designed PHP/DB CMS, that seamlessly connects (whilst cleanly separates) UX/UI elements and modular theming/display elements that are programmatically and linked intuitively. In other words, in past projects, there has always been the need to inject code/lengthy strings into templates, or manually code template elements into echo statements in PHP to sandwich between nested if-logic. And from my research and understanding the OPP-PHP-CMS community as a whole has not produced such clean implementations, often having to rely on a third "controller/viewer" layer to such models. There's got to be a better way. Ideally this design vs. programatic logic-separated CMS would also feature a modular, plug-in-play module/template system, in a dependency-worry-free, fashion. For instance each site module would consist of a folder of files: HTML template file w/ variable placeholders, .js, .css, etc., while the programatic elements would handle all aspects of the logic, including the if/else, or at the very least parse these rules within the temmplates (including loops, etc.) intuitively. Configuration for each plugin can occur between an initial install setup file, working configuration file, and an uninstall. Additionally, in order to administer the backend of these features, it would be helpful if the admin system was similarly modular, however, could intelligently inject aspects of the module into other modules/admin core in ways that are meaningful and add to the robustness of the design. In other words, it would be great to co-create, co-author an open, or closed source (either way), simple/minimalistic and yet universally applicable framework that can be ported to any new micro-site that is created for our clients' and our own needs.