Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, and the entertainment industry including: finance, distribution, representation
@eatpodcast, Jeremy, on the topic of affiliate links, it's not all too dissimilar from having a Patreon link on EatThisPodcast, especially if you have a small disclaimer somewhere, perhaps by your Patreon link. If you had affiliate links on your podcast (or in the notes) to products and services that fit within the realm of your "brand(s)" or related to the particular pieces you write/produce, I would think it to be not only appropriate, but would probably go out of my way to use them.
The problem with some who use affiliate links is that they use them to their detriment, are trying to put something over on their audience, begin over-advertising, or advertising for things outside their areas of expertise. So for example, if you had a section on Fornacalia with book reviews of some of the best books on bread, I'd probably go out of my way to use your affiliate links to purchase a few. (In fact, as a fan of bread, such a feature is one of the things I wish the site had.) It would be my simple way of paying it forward to you for sharing your years of experience with your audience, which you're not otherwise charging in any way. On the other hand, if you started promoting links to hiking equipment, it would probably leave me scratching my head or even scare me away.
I occasionally use affiliate links, but my audience is so small as for the income to be wholly negligible. At best it puts a small dent in web hosting on an annual basis. Given what you do in particular on Eat This Podcast and Fornacalia, it's a simple way of helping to defray some expenses, but might prevent you from taking other off-brand bulk advertising which would otherwise pull down the tremendous value of information you bring to your audiences. The quality of your content is certainly such that you ought to have paid advertising, but in lieu of that I can't imagine that anyone would object to a few affiliate links.
I'm curious if you have a favorite bread/baking text? I've been meaning to do more breads this year myself, but haven't had the time to research some good/technical texts. I suspect you may have all the heavy science ones on your shelf that I would be likely to purchase and could save me some time with recommendations.
Jeremy, Like you, I had some of the same issues and questions when I first started. I'd had a primary website for a while that was a bit more blog-ish on WordPress with a few other subsidiary sites for work related things. When I got into IndieWeb, WithKnown had a great plug-and play set up for almost everything, so for me, it made a nice easy place to start. I also wanted to play with Known and use it to get my feet wet. I was particularly interested in owning a lot of the shorter form posting/microblogging like Twitter without overwhelming my prior subscribers on my WordPress blog with a lot of shorter "fluff". Once I'd gotten a few things working, Known was also incredibly good at quick short posts using bookmarklets (or this mobile solution I'd come up with: http:/
Slowly over time, as I've been adding bits and pieces here and there to my WordPress set up, it has been owning more and more while somewhat less lives on my Known Install. There's also been a huge amount of community development on the WordPress side, so that it's tremendously better now than it was when I started and continues to grow. I think I hit a bigger turning point after IndieWebCamp LA when I was able to work out a bit more about how I want to own and syndicate things from my primary hub (on WordPress). (See also: http:/
Ultimately, I'd recommend doing what works best for you at the moment as there are literally hundreds/thousands of ways to pull it off. Do things one at a time in small bite-sized chunks until you have it the way you want it. There's no reason to do everything all at once. Sometimes I've found that creating posts literally by hand in raw html has been a great way to start to see both how it looks/works, and then use that experience to figure out how to best/most easily automate it going forward.
I'll also note that my coding skills were old and rusty and have been slowly getting better over time as each piece evolves. Another nice part of the process is that you'll have a chance to see how others are doing things with examples from the wiki to help you figure out what might work best for you. Over the process I've also seen others stop, change gears, and even platforms, and try out something totally different. The key seems to be to start with something you know and begin working from there based on your particular "itches" and needs [http:/
Your post was certainly a good start for taking stock of what you've got and where you might like to go. Now just make a list of your itches and do things a step at a time. I know there's an IndieWeb Cat [https:/