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

Interrupting Coders Isn’t So Bad

Here’s a hot take: disrupting coders isn’t all that bad.

Some disruptions are certainly bad but they usually aren’t. The coder community has overblown the impact. A disruption can be a good thing. How harmful disruption might be a symptom of other problems.

There are different kinds of disruptions. They are caused by other coders on your team, managers and other non-coders, or meetings throughout the day.

The easiest example to debunk is a question from a fellow developer. Imagine someone walks over to your desk or they ping you on Slack, because they have “one quick question.” Do you get annoyed at the interruption when you were in the middle of something important? You help out your teammate quickly and get back to work, trying to pick up where you left off. That’s a kind of interruption we complain about frequently, but I’m not convinced this is all that bad.

You are being disrupted but your team, of which you are only one member of the whole unit, is working smoothly. You unstuck …

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally!

I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you
don't know a lot about software development, and probably don't even know a lot about computers in general.

Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year:

Python needs LÖVE.

LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build small Lua…

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…