Diony Dashboard WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA

WordPress plugin that provides:

• branded login page styling
• branded dashboard experience
• GitHub release-based automatic updates

Repository Layout

• index.php - main plugin file
• css/ - plugin styles
• img/ - dashboard and login assets
• video/ - bundled dashboard video
• readme.txt - WordPress.org-style plugin documentation

Local Development

1. Clone the repository into wp-content/plugins/diony-dashboard.

2. Activate the plugin in WordPress.

3. Make changes in the plugin folder and test them locally.

4. 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.

1. Bump the plugin version in both the file header and the VERSION constant in index.php.
2. Commit and push the release commit to GitHub.
3. Create a Git tag that matches the plugin version, for example v1.0.2 or 1.0.2.
4. Build a ZIP package from the plugin root so the archive contains the plugin folder and files in a WordPress-installable structure.
5. Attach that ZIP as the release asset named diony-dashboard.zip.
6. Publish the GitHub release.
7. 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/, and readme.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:

1. Create and publish a GitHub release.
2. Download the release ZIP asset if needed.
3. Upload the ZIP to each site, or let the GitHub updater deliver it automatically.
4. Verify that the installed version matches the release tag.