Support and Scope

Support and scope

Dashless 1.0 is intentionally complete for a focused publishing model. This page distinguishes tested support from experiments and deliberate exclusions.

Tested environment

Component	Supported and tested target
Codex host	macOS and Linux
Windows	Editorial and Astro operations are experimental; local symlink and SSH/rsync deployment are not claimed
Node.js	22.12 or newer even-numbered releases
WordPress	6.5.9 through 7.0.3, single-site
PHP	8.0 through 8.5 syntax; compatibility CI covers PHP 8.0 and 8.4
Astro	Version resolved by the committed templates/astro/package-lock.json
Browsers	Current browsers supported by the Astro/Vite build target

The local server uses Node.js built-ins. A generated frontend requires npm and network access for its first locked dependency installation.

Additional command-line requirements depend on the operation:

• SSH deployment: ssh and rsync
• WP Cloud deployment: sftp
• Release packaging: PHP CLI, zip, and unzip
• Normal editorial work: none of those additional packaging tools

Supported editorial content

Dashless supports:

• core Posts;
• nested core Pages;
• categories and tags;
• WordPress media and accessible media metadata;
• featured images;
• normal WordPress revisions;
• draft, pending, and future editorial states;
• staged updates to already-published content; and
• exact preview and publication of an older revision.

Supported frontend behavior

• Static homepage and nested Page routes
• Story index and pagination
• Story routes
• Category/topic and tag directories and archives
• Dynamic Page navigation
• Static search
• Mirrored WordPress media
• Build-generated social cards
• RSS, sitemap, robots, canonical URLs, and structured metadata
• Responsive, accessible, light/dark presentation
• Local preview and deterministic production audit

Supported deployment targets

• An absolute local release directory with an atomic current symlink
• A remote release directory through key-based SSH and rsync
• An existing WP Cloud/Atomic site through key-based SFTP and the bundled must-use companion

WP Cloud support includes companion install or safe upgrade, immutable release upload, SHA-256 verification, atomic activation, content-generation validation, public release verification, automatic restoration after failed verification, and one-release rollback.

Deliberate 1.0 boundaries

Dashless 1.0 does not claim support for:

• WooCommerce;
• WordPress multisite;
• custom post types;
• arbitrary custom fields;
• public WordPress comments;
• page-builder reconstruction;
• team approval systems;
• unattended scheduled rebuilding;
• Windows deployment parity;
• WP Cloud account creation or purchasing;
• hosting billing;
• site provisioning;
• DNS registration or domain validation; or
• bulk email campaign delivery.

Some optional reader-signal endpoints are bundled, but the stock Astro theme does not force them into every publication. They are building blocks for a custom reader experience, not a hosted social network or marketing platform.

Scheduled publication

WordPress can move a future post to published status, and the companion records a new content generation. Dashless cannot rebuild the static site while the local computer and Codex are offline because there is deliberately no remote Dashless worker.

The next get_status call reports the stale build and deployment. deploy_frontend can then rebuild and activate the current canonical published state without republishing the post.

Credential lifecycle

Use a dedicated WordPress Application Password. disconnect_site revokes it in WordPress by default, removes its local copy, and clears site-specific workflow state while preserving content, source code, and releases.

If revocation fails, Dashless keeps the local connection so the attempt can be retried. Local-only removal must be explicitly requested and followed by manual WordPress revocation.

See Privacy and Security for storage details.