Skip to main content

Promoting Feeds by Including Treats

I've been reading an eBook in my attempts at being a better blogger and reaching a wider audience, and although I recommend it to read by anyone with similar goals, its more how I got it than what I got that I wanted to bring up. Some might know that I recently looked into ways of capitolizing on my feeds. Nearly 70% of my traffic (maybe more) is via feed subscribers, who never see my advertising. That is quite a bit of lost revenue, not that it would add up to much if they all went straight to my front page. None the less, its a problem I want a solution to. Now, I really like feeds. I don't want to make you come to my website if you prefer feeds, because I know I don't even read websites these days unless they have a feed. Even if I find a particular article I like, I typically just subscribe to the feed and wait for the article to get to me through it. Still, others are not so open to the new medium, and often treat feeds marketing. Maybe they are. These people will give you just a few lines of preview, requiring you to following the link back to the original post. Maybe they'll strip media and links from the feeds, so you need to follow back to their site to read more on the topic. There are a host of ways of turning feeds into website traffic.



That is why I found it wonderfully refreshing to see Chris Garrett actually going out of his way to entice users to subscribe to his feed in order to receive extra content that was unavailable through his website. Will this lead to a larger subscriber base? Probably. Will some portion of those readers follow back to his site from time to time? Probably. Will enticing users into a medium that is traditionally a drain on revenue and a problem for content creators who even love it actually benefit this man for his efforts? I think so.



Now, what do I have to give?



Killer Flagship Content - Free Ebook To Download @ chrisg.com



Technorati Tags:



Powered by ScribeFire.

Comments

williams said…
This was an inspiring post,Thanks for the sharing of such information deferred revenue software .

Popular posts from this blog

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…