The Insight

Content management systems are lonely places. You write in the CMS, then copy-paste to Slack to discuss. Or worse: discuss in Slack, then someone has to document decisions in the CMS.

What if the CMS was Slack?

The Build

In 24 hours, we built slacker:

  • Slack slash commands for CRUD operations
  • Message threads as content versions
  • Reactions as approval workflows
  • Bot DMs for structured content entry

How It Worked

/slacker create post "Q1 Update"
> Bot opens DM with content form
> You fill fields
> Bot posts to #content channel
> Team reacts with :white_check_mark: or :x:> Approved content auto-publishes to site

Why It Actually Made Sense

Traditional CMSs optimize for content creators. slacker optimized for teams. The context—discussions, decisions, approvals—lived alongside the content. No context switching. No lost threads.

We didn't win the hackathon, but the idea stuck. Today, tools like Notion and Coda blur the line between communication and content. We were just early.