[sirclueless]

I don't think you're "getting" their argument. The point isn't that they are incapable of understanding IFTTT. The point is that there is an entire blog post about integrating IFTTT with devices, with no description of what IFTTT is.

Reading the brief description on the About page or playing with the site for 2 minutes would solve this, but neither of those things are discoverable from the blog post.

[ThomPete]

I think I am getting their argument and I find it to be missing the point.

A blog in this context seems more to be used to tell people about where in the process a given company, service, product is.

If you are reading the blog there is a big chance that you "get" the product already.

Anyway. It's not my business. And I agree they could have an about up. But it seems to be a problem way down on the priority list. That's just my opinion of course.

[mark-r]

There are many ways to get to a blog page - Google for one, Hacker News for another. You really need some way to put it into context. Why lose the opportunity to introduce another potential user to your service?

[shawnc]

So what you're saying, is every blog post written on a products site, needs to re-introduce the product each time? That's a fair request actually, and could be achieved as simply as an opening sentence of 'If you're new here, you might want to learn about us first! CLICK HERE'

[mark-r]

No, I'm not saying there should be explicit text in the blog. I'm saying there should be a link somewhere on the page that takes you to the home page or "About Us" or "More about <product>". That's good design practice for any web site, because there's no telling how someone landed on your page. Finding a leaf node shouldn't leave you stranded.

[Bjartr]

Well, there is a link back to ifttt in the very first sentence of the blog, but something in the header or sidebar couldn't hurt I suppose.