YiiPress Documentation

Configuration

YiiPress has two separate configuration layers:

  • Content config (content/config.yaml) — site-level settings for templates and content generation
  • Engine config (config/) — Yii3 framework internals (DI, routing, middleware, environments)

Users edit content/config.yaml to customize their site. Engine config should rarely need changes.

Content config

content/config.yaml defines site-wide settings available to all templates via the $config variable.

title: My Site
description: A site built with YiiPress
base_url: https://example.com
language: en
charset: UTF-8

default_author: john-doe

date_format: Y.m.d
entries_per_page: 10

permalink: /:collection/:slug/

taxonomies:
  - tags
  - categories

image: /assets/og-default.png
twitter: "@example"

robots_txt:
  rules:
    - user_agent: "*"
      disallow:
        - /private/

params:
  github_url: https://github.com/example/mysite

Fields

  • title — site title, used in layouts, feeds, and meta tags
  • description — site description for meta tags and feeds
  • base_url — full base URL including scheme (used in feeds, sitemaps, canonical URLs)
  • language — default language code (e.g., en, ru)
  • charset — character encoding (default: UTF-8)
  • default_author — author slug (referencing a file in content/authors/), used when entries have no explicit authors field
  • date_format — PHP date format string for displaying dates in templates (e.g., Y.m.d for "2026.03.23", F j, Y for "March 23, 2026"). See PHP date format for all available format characters
  • entries_per_page — default pagination size (overridden by collection _collection.yaml)
  • permalink — default permalink pattern (overridden by collection or entry)
  • taxonomies — list of enabled taxonomy types
  • theme — default theme name for the site (see Templates)
  • image — default Open Graph image URL (absolute, or root-relative path resolved against base_url); used as fallback when an entry has no image front matter field
  • twitter — Twitter/X account handle (e.g., @example) added to twitter:site meta tag on all pages
  • robots_txt — robots.txt generation settings (see below)
  • toc — generate a table of contents from headings (default: true); set to false to disable globally. When enabled, heading tags receive id attributes and a $toc variable is passed to templates
  • search — opt-in client-side search (see below)
  • params — arbitrary key-value pairs for use in templates
  • markdown — markdown extensions configuration (see below)

Client-side search is opt-in. Enable it in content/config.yaml:

search:
  full_text: false   # index full body text (default: false, summary+tags only)
  results: 10        # max results shown (default: 10)

When enabled, the build generates a search-index.json file in the output directory and injects a search button into the site header. Clicking the button (or pressing Ctrl+K / ⌘K) opens a search modal with fuzzy matching. No external dependencies — everything is hand-rolled JavaScript.

The full_text option controls how much content is indexed:

  • false — indexes title, summary, and tags (smaller index, faster)
  • true — additionally indexes the full body text (larger index, more thorough results)

robots.txt

A robots.txt file is generated by default with a permissive rule (allow all crawlers) and a Sitemap: pointer. Configure custom rules via robots_txt:

robots_txt:
  generate: true   # set to false to disable robots.txt generation entirely
  rules:
    - user_agent: "*"
      disallow:
        - /private/
        - /admin/
      crawl_delay: 5
    - user_agent: "Bingbot"
      allow:
        - /
      disallow: []

Each rule supports:

  • user_agent — crawler name (default: *)
  • allow — list of allowed paths
  • disallow — list of disallowed paths
  • crawl_delay — seconds between requests (integer)

Usage in templates

Currently, the entry template receives individual variables ($siteTitle, $entryTitle, $content, $date, $author, $collection). Full $config access in templates is planned for the theming system.

Markdown settings

The markdown section controls which Markdown extensions are enabled. All options are boolean.

markdown:
  tables: true
  strikethrough: true
  tasklists: true
  url_autolinks: true
  email_autolinks: true
  www_autolinks: true
  collapse_whitespace: true
  latex_math: false
  wikilinks: false
  underline: false
  no_html_blocks: true
  no_html_spans: true
  permissive_atx_headers: false
  no_indented_code_blocks: false
  hard_soft_breaks: true
  • tables — GitHub-style tables (default: true)
  • strikethrough — strikethrough with ~text~ (default: true)
  • tasklists — GitHub-style task lists (default: true)
  • url_autolinks — recognize URLs as auto-links even without <> (default: true)
  • email_autolinks — recognize e-mails as auto-links even without <> and mailto: (default: true)
  • www_autolinks — enable WWW auto-links (even without any scheme prefix, if they begin with 'www.') (default: true)
  • collapse_whitespace — collapse non-trivial whitespace into single space (default: true)
  • latex_math — enable LaTeX math spans $...$ and $$...$$ (default: false)
  • wikilinks — enable wiki-style links [[link]] (default: false)
  • underline — underscore _ denotes underline instead of emphasis (default: false)
  • no_html_blocks — disable raw HTML blocks (default: true)
  • no_html_spans — disable inline raw HTML (default: true)
  • permissive_atx_headers — do not require space in ATX headers ( ###header ) (default: false)
  • no_indented_code_blocks — disable indented code blocks (only fenced code works) (default: false)
  • hard_soft_breaks — force all soft breaks to act as hard breaks (default: true)

If the markdown section is omitted, all defaults apply.

Defaults and overrides

Collection _collection.yaml fields override content config defaults:

  • Collection entries_per_page overrides config.yaml entries_per_page
  • Collection permalink overrides config.yaml permalink
  • Entry permalink overrides collection permalink

Resolution order: entry → collection → content config → engine defaults.

Engine config

The config/ directory contains Yii3 framework configuration:

  • config/common/ — DI containers, routes, aliases, bootstrap
  • config/web/ — web-specific DI and params
  • config/console/ — console-specific params and commands
  • config/environments/ — environment overrides (dev, test, prod)

Engine config controls framework internals: routing, middleware, dependency injection,
asset management, and view rendering. It is not exposed to templates.