Why I Stopped “Creating Content”

This is a repost promoting content originally published elsewhere. See more things Dan's reposted.

The first time I saw Michelangelo’s David in person, I wept. Never in my life have I witnessed a more beautiful piece of content.

I wasn’t the only one who felt that way. Museum patrons all around me were looking up from their phones to admire David as well. Despite it being legacy content, David was so scrollstoppingly captivating that it generated stronger engagement than TikTok and Instagram combined, despite those platforms offering fresher, more personally relevant content.

My awe only grew when I noticed the museum gift shop converting 60% of its traffic, numbers that would make any content creator salivate.

In case it wasn’t obvious that Michael was being facetious (oh god, please let it be obvious), he says as much right after this introduction.

The point is: ‘content‘ have become a catch-all term so broad as to be meaningless. A tweet is content. A Netflix series is content. Everything in-between that is passively or mostly-passsively consumed is content, whether it’s AI-slop music or template-driven memes. And content exists to trigger engagement and drive traffic and oh shit now we’re down a rabbithole of meaningless SEO jargon.

Like Michael, I don’t like it. These different media are fundamentally different, and we should embrace that. A blogger is not (necessarily) a documentarian, nor are they a comic book artist or an exhibition curator or a podcaster. They can be all of those things, but they’re different things! When we treat them all as interchangeable kinds of “content” for a generic “audience”, we lose something about what’s beautiful and unique about each of them… and we lose the opportunity to find and name new art forms at the intersections between them.

You can call things “content” if you like, but the vocabulary available to us is richer than that, and the things we create – in whatever form they take – can be too, when we use it.

0 comments

    Reply here

    Your email address will not be published. Required fields are marked *

    Reply on your own site

    Reply elsewhere

    You can reply to this post on Mastodon (@blog@danq.me).

    Reply by email

    I'd love to hear what you think. Send an email to b30097@danq.me; be sure to let me know if you're happy for your comment to appear on the Web!