Diony Dashboard releasesself-updates
A WordPress plugin built to modify the WP dashboard, applying Diony branding and links.
by Diony Creative Ltd · github.com/dionyteam/diony-dashboard · website
Install
The author publishes release zips, so WP-CLI can install straight from GitHub:
wp plugin install https://github.com/dionyteam/diony-dashboard/releases/download/2.0.1/diony-dashboard.zipShips its own WordPress updater (built-in updater), so new versions show up under Dashboard → Updates.
WordPress plugin that provides:
- branded login page styling
- branded dashboard experience
- GitHub release-based automatic updates
Repository Layout
index.php- main plugin filecss/- plugin stylesimg/- dashboard and login assetsvideo/- bundled dashboard videoreadme.txt- WordPress.org-style plugin documentation
Local Development
-
Clone the repository into
wp-content/plugins/diony-dashboard. -
Activate the plugin in WordPress.
-
Make changes in the plugin folder and test them locally.
-
Run a syntax check before release:
php -l index.php
Release and Deployment
Use GitHub Releases as the single source of truth for distributing updates.
- Bump the plugin version in both the file header and the
VERSIONconstant inindex.php. - Commit and push the release commit to GitHub.
- Create a Git tag that matches the plugin version, for example
v1.0.2or1.0.2. - Build a ZIP package from the plugin root so the archive contains the plugin folder and files in a WordPress-installable structure.
- Attach that ZIP as the release asset named
diony-dashboard.zip. - Publish the GitHub release.
- Allow WordPress to pick up the new release through the built-in updater logic.
Packaging Rules
- The ZIP asset should contain the plugin files at the top level of the plugin folder.
- The archive should include
index.php,css/,img/,video/, andreadme.txt. - Do not upload a raw source archive unless it matches the expected plugin folder structure.
- Keep the release asset name consistent so the updater can find
diony-dashboard.zip.
Updating Installed Sites
For client sites, you can upload the release ZIP directly through the WordPress plugin uploader.
You do not need to git clone the repository onto each site.
Recommended workflow:
- Create and publish a GitHub release.
- Download the release ZIP asset if needed.
- Upload the ZIP to each site, or let the GitHub updater deliver it automatically.
- Verify that the installed version matches the release tag.
Releases
6 releases. Each count is every asset in that release; expand a row for the breakdown.