Skip to content

Features

Features

GENNAI treats installation, publishing, extension and operation as independent parts that fit together. Start reading wherever you need.

Install

Get started as quickly as WordPress

Run a single command, then follow the setup wizard in your browser. Everything you need to go live — from the site name to analytics tags and referral destinations — is configured in one pass.

  • ./install.sh brings up the whole Docker stack (Laravel 12 admin, Next.js 14 front end, MySQL)
  • Finish the initial configuration in an 8-step wizard
  • Configure everything from the browser, much like the WordPress installer

The 8 steps of the setup wizard

  1. 1Site basics
  2. 2Administrator
  3. 3Operator information and publishing rules
  4. 4Theme and brand
  5. 5Analytics (GA4, GTM, Search Console)
  6. 6Referral CTA
  7. 7Plugins
  8. 8Review and finish

Static Export

Your public site is just HTML

Once you write an article, Next.js static export generates the HTML you serve. The admin and database never sit on the public side, so pages stay light and the attack surface stays minimal.

  • Deploy as-is to S3 + CloudFront or any other static host
  • The admin (CMS) is never exposed to the internet
  • No server-side processing, so pages load fast

Plugins & Themes

Rearrange freely with plugins and themes

Plugins add features; themes control the look. Both can be switched from the admin. If you know WordPress, the same mental model applies.

  • Plugins have two layers — Laravel and Next.js — and are enabled or disabled in the admin
  • Scaffold a new one with php artisan plugin:make
  • Themes are made of tokens.css, overrides.css and swappable parts, and are switched in the admin

Plugins = parts for features

  • laravel/plugins/<id>/
  • frontend/src/plugins/<id>/

The admin side and the site side are enabled or disabled together as a single plugin.

Themes = parts for the look

  • tokens.css
  • overrides.css
  • components/

Built from color and typography tokens, override CSS, and swappable parts.

Front Page

Build your home page by arranging parts

Manage the home page as a static page and compose it in the admin by arranging section parts such as the hero, article lists, categories and CTAs. It works much like WordPress's “Your homepage displays” setting.

  • Rebuild the home page just by rearranging section parts like building blocks
  • Change the priority of features and calls to action without touching code

Compliance

Pre-publish checks, built into the system

On every build, all pages are checked automatically, and the build stops before publishing if anything violates the rules. Whether to show an ad disclosure (PR label), and its wording, is up to the operator in the admin's site settings.

  • Detects words that must not appear on public pages, such as the operator's name
  • Checks that a 404 page exists and that no internal links are broken
  • Check rules are edited through the admin GUI

The ad disclosure (PR label) is optional. Whether to show it and its wording are set in the admin's site settings, and themes can change how it looks.

SEO & Analytics

SEO and analytics from day one

GA4, GTM and Search Console settings live together in the admin, and sitemaps, SEO reports and click tracking for referral buttons come built in.

  • GA4 / GTM / Search Console settings
  • Sitemap generation and SEO reports
  • Conversion (CTA click) tracking and redirect management
  • Internal links are checked at build time to prevent broken links

Security

Secure by default

The public side is static HTML only. On top of that, the admin ships with defaults that err on the side of safety.

  • Login bypass from your internal network is limited to registered domains (off by default)
  • The public settings API uses an allowlist and returns only the fields that are needed

MCP / API

Grow your media together with AI agents

Articles, parts, tasks and the wiki can all be operated through an HTTP API (MCP). Hand writing and updates to AI agents while people focus on review and decisions.

  • Read and write articles, parts, tasks and the wiki via the API
  • Agents work with the same data you manage in the admin

The documentation walks through the setup process in detail