Skip to content
GetmeDocs
Sign inCreate account

Getting started

  • Getme developer documentation

API Reference

  • Introduction
  • Authentication
  • Errors
  • Idempotent requests
  • Metadata
  • Pagination
  • Request IDs
  • Versioning
  • Webhooks
  • Event Catalog
  • SDKs and CLI

Core Resources

  • Auth
  • Events

Site Resources

  • Forms
  • Sites

Commerce Resources

  • Brands
  • Categories
  • Products
  • Services

Crm Resources

  • Customers

Other Resources

  • Media

Dev Tools

  • CLIBeta
  • Website source with the CLIBeta
  • Webhooks with the CLIBeta
  • SDKsBeta
  • Node SDKBeta
  • Python SDKBeta

Guides

  • Guides
  • Quickstart
  • Website source workflow
  • Webhook handler

Changelog

  • Changelog
  • June 10, 2026 - Developer platform docs beta
  • July 15, 2026 - Install token lifecycle safety
  • July 15, 2026 - Source-first site development
  • July 15, 2026 - Site source navigation warnings
Loading documentation...
HomeChangelogJuly 15, 2026 - Site source navigation warnings

July 15, 2026 - Site source navigation warnings

Find unresolved navigation page targets without blocking valid source sync and deploy workflows.

Site source validation now reports an enabled navigation page_key that does not resolve to an enabled page-registry entry as a classified warning.

Affected surfaces

  • Developer API
  • CLI
  • Docs

Changes

  • Validation responses include theme_navigation_target_missing in warnings[] with navigation category, warning severity, parameter path, and source context.
  • Nested navigation items are checked using registry paths declared by the theme; arbitrary URL links are not treated as page-registry targets.
  • Warnings leave valid=true and do not block source save, preview, package, deploy, or owner-gated publication.
  • The CLI prints warnings to stderr and continues without an interactive confirmation. Validation errors remain blocking.

Developer action

Review warnings and either add/enable the target page-registry entry or remove the stale navigation target. No client migration is required.

See Website source workflow and Website source with the CLI.

On this page

  • Affected surfaces
  • Changes
  • Developer action