17‑file content engine hack

A viral how-to post argued one person can run a multi-account social operation from a tiny stack of text files and automation rules. (x.com) The recipe is simple in structure: store prompts, brand rules, calendars, and post templates as plain Markdown or YAML files, then let an automation tool turn those files into scheduled posts. GitHub Actions describes this pattern as frontmatter for configuration plus Markdown instructions in natural language. (github.blog) The social version of that pattern is already visible in public workflow repos. One GitHub project uses n8n, Airtable, Replicate, Placid, and Google Drive to move a post from idea to generated asset to scheduled distribution. (github.com) Another public n8n project automates the full pipeline for short-form video: OpenAI writes the script, ElevenLabs generates narration, OpenAI creates images, and FFmpeg assembles the finished clip for YouTube Shorts and Instagram Reels. (github.com) The point of the 17-file pitch is not that Markdown itself posts to social networks. The files act like a compact control panel: one file for voice, one for offers, one for platform rules, one for schedules, and others for prompts, approvals, and publishing logic. (github.blog) That matters in 2026 because the surrounding tooling has become cheap and modular. A YouTube tutorial published March 9, 2026 said one creator used “one yaml file” to run 6 brands, 18 social accounts, and 12 posts a day with automatic staggering by posting time. (youtube.com) The orchestration layer is usually n8n, an open-source automation tool that connects application programming interfaces the way Zapier or Make do, but with more control for self-hosting. A large GitHub template library now lists more than 280 ready-to-import n8n workflows, including Instagram, Twitter, and other social media automations. (github.com) In practice, these systems split the job into repeatable steps: generate draft text, create or fetch media, format captions for each platform, queue posts, and stagger publish times so every account does not fire at 9 a.m. The March 2026 tutorial said that timing fix was necessary after an early version posted all 12 items at once. (youtube.com) The strongest case for the approach is cost and control. Public project authors describe custom pipelines as cheaper than agency retainers or credit-based video tools, and they keep prompts, assets, and workflow logic in files the operator can version, edit, and reuse. (youtube.com) (github.com) The weak point is that a compact file system does not replace the hard parts of publishing. The public repos still depend on separate services for images, narration, templates, storage, approvals, and network-specific posting, and each service needs credentials, rate-limit handling, and human review. (github.com 1) (github.com 2) So the “17 files” claim is best read as an operating model, not a literal law of content. A small set of text files can define the machine, but the machine still runs on APIs, schedulers, and someone willing to keep tuning it. (x.com)