--- title: 'WordPress or flat-file: how to choose for a marketing site in 2026' url: 'https://mountainairweb.com/blog/wordpress-or-flat-file-for-a-marketing-site' markdown: 'https://mountainairweb.com/blog/wordpress-or-flat-file-for-a-marketing-site.md' date: '2026-07-22' description: 'Short answer: if your site is a marketing site under a few hundred pages, has a small number of editors, and you care about speed, security and being readable by AI assistants, a flat-file CMS is now a serious option. If you need e-commerce, memberships, many authors with workflows, or a plugin eco…' taxonomy: category: - WordPress --- [WordPress](https://mountainairweb.com/blog/category:WordPress) July 22, 2026 4 min read # WordPress or flat-file: how to choose for a marketing site in 2026 We build both. Here is the comparison we walk clients through before recommending either, including the cases where the answer is obvious. Nicholas Murray Author **Short answer:** if your site is a marketing site under a few hundred pages, has a small number of editors, and you care about speed, security and being readable by AI assistants, a flat-file CMS is now a serious option. If you need e-commerce, memberships, many authors with workflows, or a plugin ecosystem your team already depends on, WordPress remains the right call. Most companies can decide in one meeting with the five questions at the end of this post. ## What "flat-file" means A flat-file CMS stores every page as a text file (Markdown with a block of settings at the top) instead of rows in a database. Grav is the one we build on. There is no MySQL, no `wp_options` table, no SQL injection surface. Backing up a site means copying a folder. Rolling back a change means `git revert`. The admin is a separate app that talks to the site through an API with per-user permissions. That sounds like a developer’s preference, and it is, but the reason it matters to a marketing team is what it removes: database maintenance, most of the plugin-update churn, and a hosting bill sized for WordPress. ## Where each one wins | Your situation | WordPress | Flat-file (Grav) | |---|---|---| | Marketing site under ~200 pages | Fine | Fine, cheaper to run | | Many authors, roles, editorial workflow | Strong | Simpler permissions | | Marketo, HubSpot, 6sense, GTM embeds | Yes | Yes | | E-commerce, memberships, LMS, events | Yes | No | | Content reviewed in pull requests | With effort | Native | | Every page readable as Markdown by AI | Needs a plugin | Built in | | Database to secure and back up | Yes | None | | Plugin ecosystem your team already knows | Huge | Small | | Typical hosting | Managed WordPress tier | Small VPS | ## The AI-readability point, specifically AI assistants and answer engines read your site to decide whether to recommend you. They read visible text and structured data; they do not care about your CMS. But a flat-file site built the way we build them serves every page as clean Markdown at `/page.md` (try it on this site), exposes an MCP server so agents can read content with permissions, and ships `llms.txt` and structured data by default. On WordPress you can get most of this with the right plugins and a developer who sets them up; it just isn’t the default. ## The editing experience is the real question The objection we hear most is "our team can’t edit text files." They don’t have to. The visual builder we ship with flat-file sites lets editors click into a heading and type, reorder sections, swap images and add new sections from a library. It is closer to a modern block editor than to a code repository. The trade-off is that very large editorial operations, with dozens of contributors and scheduled publishing across roles, are still better served by WordPress. ## Cost over three years The build cost is similar either way; the work is in the design, content model and integrations, not the CMS. The difference shows up in year two and three: managed WordPress hosting, a security and update plan, and plugin licences versus a small server and a lighter care plan. For a 60-page company site, the flat-file total is usually meaningfully lower. For a site that leans on commercial plugins, WordPress’s ecosystem pays for itself. ## Five questions that settle it 1. **Do you sell anything, gate anything with accounts, or run events through the site?** Yes → WordPress. 2. **How many people publish each month, and do they need approval workflows?** More than a handful with workflows → WordPress. 3. **Is there a plugin your team cannot live without?** Yes → WordPress. 4. **Is the site mostly pages, a blog and a few forms?** Yes → flat-file is on the table. 5. **Does leadership ask whether ChatGPT recommends you?** Either works, but flat-file gets you there with less configuration. If you answered "no" to the first three and "yes" to the fourth, ask for a flat-file quote next to the WordPress one. We will give you both and tell you which we would pick for your site. If you want a second opinion on an existing site first, the [free audit](https://mountainairweb.com/free-audit) covers platform fit. ## More from the journal [See all posts](https://mountainairweb.com/blog) WordPressSep 16, 2026 ### Headless WordPress in 2026: why we usually say no (and what we recommend instead) Headless WordPress doubles your systems, drops the editor preview and most plugins, and the reasons people wanted it… [Headless WordPress in 2026: why we usually say no (and what we recommend instea…](https://mountainairweb.com/blog/headless-wordpress-in-2026) WordPressSep 9, 2026 ### What a WordPress maintenance plan should actually cover (and what most leave out) Hosting plans, cheap update subscriptions and developer care plans all call themselves WordPress maintenance. What each covers, the… [What a WordPress maintenance plan should actually cover (and what most leave ou…](https://mountainairweb.com/blog/what-a-wordpress-maintenance-plan-should-cover) WordPressAug 5, 2026 ### WordPress security in 2026: what your IT team will ask, and the honest answers 11,334 WordPress vulnerabilities in 2025, 91% of them in plugins, median five hours from disclosure to exploitation. Here… [WordPress security in 2026: what your IT team will ask, and the honest answers](https://mountainairweb.com/blog/wordpress-security-for-marketing-teams) --- ## Navigation - Parent: [Blog](https://mountainairweb.com/blog.md) - Previous: [WCAG 2.2 for marketing websites: what changed, what the law says, what it costs to ignore](https://mountainairweb.com/blog/wcag-2-2-for-marketing-websites.md) - Next: [What to ask a white-label developer before the first project](https://mountainairweb.com/blog/what-to-ask-a-white-label-developer.md)