# Docusaurus 3.10.2: make probe. Each probe page built alone: probe.mdx imports the # native variables module (src/vars.js), probe-json.mdx the book's file as JSON. # A name the file does not define (no_such_name), a key with no value (ssl), # and a defined name, each between brackets. == probe.mdx exit status 1 Can't render static file for pathname "/probe" Variable not defined: vars.no_such_name == probe-json.mdx exit status 0 Undefined: [] empty: [] defined: [ # A page with no front matter and a heading '# {vars.app_runtime_abbr} Component Metrics', # which Docusaurus takes as the page title (scratch page probe2.mdx, built alone, # 2026-10-11): the heading shows the value, the the expression's source. <title data-rh="true">{vars.app_runtime_abbr} Component Metrics | Notes round — Docusaurus <h1>Cloud Foundry<!-- --> Component Metrics</h1> # With the site's heading plugin (heading-vars.js), 2026-10-11, scratch pages built alone. # A heading '## About {vars.no_such_name} {#about}': exit status 1 Error: MDX compilation failed for file ".../undef/undef.mdx" Cause: Variable not defined as text: vars.no_such_name in .../undef/undef.mdx # The page above with '# {vars.app_runtime_abbr} Component Metrics' as its title: the plugin # writes the value into the heading and the table of contents, but Docusaurus takes the title # from the source first, so the <title> and the sidebar still show the expression's source. <title data-rh="true">{vars.app_runtime_abbr} Component Metrics | Variables round — Docusaurus toc: About Cloud Foundry | Metrics in Cloud Foundry