How We Ship Blog Posts with Slack Approval

Most marketing sites treat blogging as either fully manual or fully automated. Manual is slow. Fully automated skips taste. We wanted a middle path for Brutanix Studios: write on a schedule, review in a private Slack channel, and only publish when someone explicitly says so.

Draft in the repo, not a CMS

Our posts live in the same Next.js codebase as the site. That keeps SEO metadata, structured data, and the article body in one place — and a pull request becomes the review artifact. No separate CMS login, no sync drift between content and deployment.

Approve where the team already is

When a draft PR is ready, we post the title, a short summary, and the PR link to a private Slack channel. A reply of "post it" is the merge signal. That keeps approval lightweight without making the channel public to the whole workspace.

• Scheduled drafting twice a week
• Private Slack review instead of email threads
• Merge publishes through the normal Vercel deploy

“The best content workflow is the one your team will actually use on a Tuesday afternoon.”

What ships

After merge, the portfolio redeploys with the new post already wired for titles, descriptions, Open Graph, and sitemap entries. Same quality bar as a hand-written article — just a faster path from idea to live URL.