⚡ DEMO FREE — preview version. Go to Pro →
🔥 VERSION 1.0 (DEMO FREE)

Static site with AI visibility out of the box

Store your content in Markdown on GitHub — get a fully optimized site with JSON-LD, sitemap, Open Graph, and a load time of under 200 ms. No databases, no dependencies.

AI-ready markup 50+ sitemap URLs Schema.org JSON-LD 0 databases
≤200ms
Server Response Time (TTFB) with VPS
2.8s
Build of 50+ pages (Vite SSG)
100%
Lighthouse SEO & Performance Score

GitHub CMS enables companies to create content with visibility in neural networks — ChatGPT, Perplexity, Google AI Overviews. No databases, no monthly SaaS fees, no development team needed. Markdown articles automatically get JSON-LD markup, Open Graph tags, and land in the sitemap on every push to the repository.

Recognize yourself?

GitHub CMS is built for those who need a working, fast, and secure site, rather than endless plugin configuration and subscription fees.

DEVELOPER / INDIE HACKER
👨‍💻

"The code is written. Product is ready. No site. No budget for a designer either."

You wrote a brilliant product — months of coding, microservices, architecture. It's time to launch. But you need a showcase site right now. Figma, Photoshop, and Webflow layouts are not your element. A freelance designer asks for $500 and 2 weeks. An agency asks for $3,000.

GitHub CMS is your native environment. You don't have to learn proprietary admin panels or suffer with visual builders. The workflow comes down to standard git commits. Continuous Integration handles the routine: validates content, builds the frontend, and delivers artifacts to the server.

  • Familiar environment: Git + Markdown + CI/CD
  • Full code control (Vue 3 + Vite)
  • Painless deployment in 5 minutes
  • MIT License — free forever
SMALL BUSINESS / STARTUP
🏪

"Need a site now. Everyone asks for money. And then every month for SaaS."

A WordPress agency offers a site for $1,000 and 3 months of development. Builders cost $20/month, and you don't own the code. Enterprise CMS is expensive, slow, and requires an in-house developer. And then come the plugins, vulnerabilities, form hacks, MySQL server crashes...

GitHub CMS shifts the project economics. You pay only for a basic server, while all metadata generation infrastructure (which requires premium plugins elsewhere) works out of the box. Serverless architecture cuts off 99% of hacking threats, removing the need to hire a sysadmin for regular audits.

  • Independence from website builder pricing policies
  • Maximum security (0 CMS vulnerabilities)
  • Flawless speed for clients (TTFB < 200ms)
  • Ready structure to grow into an online store

How it works under the hood

GitHub CMS architecture relies on 4 accepted ADRs (Architecture Decision Records). No magic, just engineering pragmatism and strict contracts.

---
title: "How to speed up loading"
slug: "speed-up"
date: "2026-05-22"
schema_type: "Article"
geo:
  answerfirst: "Use CDN and SSG."
  keyfacts:
    - "TTFB affects ranking. verified"
---

<!-- block answer-first –> To speed up, use Static Site Generation… <!-- /block answer-first –>

1. The Frontmatter Contract

Every page or article is a Markdown file with a YAML header. This structure is parsed by the gray-matter utility. Fields are strictly typed: if you forget to specify slug or title, GitHub Actions will halt the build and point out the error.

A special geo block allows you to embed semantic annotations directly into the file. During the build (SSG), this information is transformed into a valid JSON-LD graph linking entities, facts, and authors.

name: Build and Deploy
on:
push:
branches: ["main"]
jobs:
build:
runs-on: ubuntu-latest
steps: - uses: actions/checkout@v4 - run: npm install - run: npm run validate - run: npm run build - run: rsync -avz dist/ user@server:/var/www/html/

2. Continuous Integration (CI/CD)

GitHub CMS requires no manual builds. With every git push to the main branch, the pipeline triggers. First, the validate.ts script checks all Markdown files against the rules (no secrets, required blocks present, meta tag lengths).

Then Vite SSG runs, rendering Vue components into static HTML. The resulting dist/ folder is copied to your server via SSH. No Node.js or PM2 in production.

Generative Engine Optimization

The era of plain SEO is fading. People don't just look for links on Google; they ask questions directly to ChatGPT, Perplexity, Claude, and Bing Copilot. For your site to appear in their answers (and provide a link to you), your content must be structured specifically. This is called GEO.

  • 1
    Direct answer. The answer-first block gives the AI model a clear, unambiguous answer without fluff or preamble.
  • 2
    Fact verification. The verified markers tell parsers the fact is backed by sources (E-E-A-T).
  • 3
    Linked data. Automatic microdata generation links the article to its Author and Organization.

Generated JSON-LD Payload (Example)

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "@id": "https://githubcms.ru/#webpage",
      "url": "https://githubcms.ru/",
      "name": "GitHub CMS",
      "isPartOf": { "@id": "https://githubcms.ru/#website" }
    },
    {
      "@type": "Article",
      "@id": "https://githubcms.ru/#article",
      "headline": "Static site with AI visibility",
      "datePublished": "2026-05-22T00:00:00+00:00",
      "author": {
        "@type": "Person",
        "name": "GitHub CMS Team"
      }
    }
  ]
}

Platform Comparison

How GitHub CMS compares to monoliths and builders.

Criteria WordPress (Managed) SaaS Builder GitHub CMS
Database MySQL (Vulnerabilities) Closed platform DB None (Git repository)
Response speed (TTFB) 400 - 1200 ms (Cache dependent) 200 - 500 ms ≤ 200 ms (Nginx static)
JSON-LD Generation Paid plugins (Yoast/RankMath) Basic or manual Automatic (10+ types)
Code ownership Full (but lots of legacy) Vendor Lock-in (you don't own code) 100% Ownership (MIT license)
Security (Hacks) High risk (Bruteforce, SQLi) Medium (platform handles) Zero risk (No backend)
Total Cost of Ownership $300 – $1200 / yr (Hosting+Plugins) $180 – $400 / yr (Subscription) ~$40 / yr (VPS only)

One Repository — Dozens of Tasks

Thanks to the flexible template system and Markdown, you can adapt the site to any small business or IT project needs.

🚀

SaaS Landing Page

Quick launch of a startup presentation page. Integration of lead forms via third-party services, instant loading on mobile devices.

🏪

Service / Business Site

For lawyers, consultants, agencies. Service Schema.org generation allows search engines to correctly understand prices and service regions.

📝

Blog / Media Resource

A full-fledged content engine with tags, categories, pagination, and RSS feed generation. Perfect for SEO traffic.

🛒

Showcase / Simple Store

Create products as .md files. Product Schema.org is generated automatically. Connect Stripe, PayPal, or local payment iframes.

📚

Tech Documentation

Built-in support for code syntax highlighting, navigational indexes, and structured TechArticle markup.

🌍

Multilingual Sites

Organize content by folders (en, es) with automatic hreflang tag generation for proper international SEO.

Complete Knowledge Base & FAQ

Everything you need to know about frontmatter, deploy, JSON-LD, and architecture.

Which Frontmatter fields are required?

There are 4 required fields: title (≤70 chars), description (120-160 chars), slug (latin, digits, hyphens), date (YYYY-MM-DD). Without them, content validation at build time will fail. These fields form the H1, meta-description, URL, and publish date in the sitemap.

How does author affect JSON-LD?

The author field automatically generates a JSON-LD Person entity with fields: name, url, image, sameAs, worksFor. AI search engines parse this to see who wrote the article, their experience, and affiliations. This is a powerful E-E-A-T signal.

What schema_type values are supported?

The system supports many types: Article, HowTo (generates complex JSON-LD with steps), FAQPage (extracts Q&A from content), BlogPosting, NewsArticle, TechArticle, Product, Service, WebSite. Build validation strictly checks against this list.

Why is the raw_html field needed?

The raw_html: true flag disables standard markdown-it rendering. The body of the .md file is used directly as pure HTML. This is critical for landing pages (like the one you are reading) built with Bootstrap classes and inline styles.

How do tags and categories affect the site?

The tags and category fields automatically generate routes like /tag/name/ and /category/name/. Each becomes a paginated list of articles. In JSON-LD, tags are passed to about/mentions, and categories to articleSection. Validation ensures tags is an array.

How is Frontmatter validated during build?

Over 10 tests run: title length, valid slug format, ISO dates, allowed schema types. Critically, if the parser finds secret keys (VITE_*, SECRET_*) in Frontmatter, it aborts the build, protecting you from accidental API key exposure in public HTML.

Can I add custom Frontmatter fields?

Yes. Any additional YAML fields are parsed and available inside Vue components via the page object. You can add price: 1500 or custom_color: "#ff0000" and use it in your template. Standard fields are handled by useSeo.ts.

What happens if Frontmatter is empty?

Without required fields, the CI/CD pipeline (GitHub Actions) will fail, preventing a broken site from reaching the server. Missing recommended fields simply reduces your SEO/GEO potential by up to 60%, as search engines miss crucial E-E-A-T signals.

How can a developer launch a site without a designer?

Clone the GitHub CMS repo, edit Markdown files in content/, and git push. GitHub Actions automatically builds and deploys the site to your VPS. No Figma, no UI developer needed — the box includes a mobile-ready UI with correct typography and spacing.

How much does it cost for a small business?

TCO approaches zero. The engine is MIT licensed. The only recurring expense is standard cloud VPS hosting (~$40/yr). You do not pay for CMS tiers, visual editor licenses, or caching plugins. Everything is built into the Vite SSG process.

Do I need a programmer to regularly update articles?

No. Content is edited as regular text files right in the GitHub.com interface. Just click "Add file" in the content/blog/ folder, paste text based on the template, and commit. The site updates automatically in the background in 2-3 minutes.

Is a static site secure compared to WordPress?

It is fundamentally more secure. WordPress runs a PHP interpreter and a MySQL database. A hacker can execute an injection via a plugin flaw or brute-force the /wp-admin panel. A static site is just HTML files — nothing to hack, nowhere to execute malicious code.

Fundamental Advantages of Static Architecture

Moving away from classic CMS is not just about saving on hosting. It is a fundamentally new approach to security, speed, and business independence from paid plugin ecosystems.

The Design Problem

Many tech specialists hesitate to hire designers just to build a product landing page. They can code, but don't want to spend weeks on visual systems, grids, and FAQ blocks. GitHub CMS removes this friction: instead of a blank canvas, you get a pre-designed section system that can be improved iteratively.

The Cost Problem

When starting a business, every subscription hurts. Usually, a site brings a cascade of costs: template, builder, premium SEO add-on, CDN, antispam, and someone to fix it all. A static site avoids this cascade: the infrastructure is simpler, and the TCO is significantly lower.

The Maintenance Problem

In traditional systems, traffic spikes mean stress: tweaking Redis, fighting slow SQL queries, and worrying about DDoS. The static paradigm solves this. Serving pre-generated files via Nginx or CDN allows the project to handle colossal loads without configuration changes.

Ready to launch your site?

Clone the repository, edit the Markdown files, and set up your deployment following the guide. Your AI visibility starts here.