> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# WordPress Control Surface

> A first-class operational surface for direct WordPress projects: overview, narrow safe actions, diagnostics, and recent history.

<Tip>
  **Live.** This area is documented as current, user-reliable behavior.
</Tip>

## Goal

Operate a StackShift-hosted WordPress site without leaving StackShift for routine checks.

## Prerequisites

* A direct WordPress project

## Workflow

<Steps>
  <Step>
    Open the project overview to see runtime, DB, storage, and plugin state.
  </Step>

  <Step>
    Run safe actions (reset password, flush permalinks, maintenance mode, flush cache, DB upgrade, core update).
  </Step>

  <Step>
    Review the operational history list for recent changes and outcomes.
  </Step>
</Steps>

## The overview

The control surface reads live metadata from the site: runtime status, database, storage, and installed plugin and theme state. It is the place to check how a WordPress site is doing without opening wp-admin or the node.

## Safe actions

A narrow set of safe operational actions runs against the site and is audit-logged in the history list.

* Reset the admin password.
* Flush permalinks.
* Enable or disable maintenance mode.
* Flush the object cache.
* Run a database upgrade.
* Update the WordPress site URL.
* Update WordPress core.

## Themes, staging, and history

* Install and activate themes from the WordPress theme marketplace.
* Clone a staging copy of the site to test changes.
* Review the operational history to see recent actions and their outcomes.

## Expected result

<Check>
  Operators see WordPress runtime state and recent operations directly in StackShift, with every safe action audit-logged.
</Check>

## Related guides

<CardGroup cols={2}>
  <Card title="Deploy WordPress on StackShift" href="/wordpress/deploy-wordpress-on-stackshift">
    Launch single-site WordPress as a template-backed stack with bundled MariaDB and persistent storage.
  </Card>

  <Card title="Back up and restore a WordPress stack" href="/wordpress/back-up-and-restore-a-wordpress-stack">
    Use StackShift stack backups for WordPress content and bundled MariaDB data, then validate the app after restore.
  </Card>

  <Card title="WordPress plugin and theme releases" href="/wordpress/wordpress-plugin-theme-releases">
    Connect a WordPress plugin or theme repo, let StackShift package it into a release, preview it, promote draft/beta/stable channels, and install the exact release on a running StackShift WordPress site.
  </Card>
</CardGroup>