## Summary Reorganized root directory structure to separate active development files from legacy artifacts and improve project maintainability. ## Changes Made - **Archive Structure**: Created `archive/` with organized subdirectories: - `deployment-history/` - Old wordpress-dev and deployment artifacts - `legacy-docs/` - Historical documentation files - `temp-scripts/` - Temporary configuration and test files - `old-tests/` - Previous test results and logs - `memory-bank/` - AI context files - `zoho-crm/` - CRM field definitions - **Essential Files Restored**: - Core plugin files (`hvac-community-events.php`, `includes/`, `templates/`, `assets/`) - Configuration files (`.env`, `composer.json`, `phpunit.xml`) - Active deployment scripts in `scripts/` directory - **Updated Documentation**: - Updated CLAUDE.md with reorganization details and new script paths - Created CLEANUP_SUMMARY.md documenting the changes ## Verification - ✅ Plugin redeployed successfully after reorganization - ✅ All critical functionality verified working - ✅ Certificate reports, dashboard, and login pages accessible - ✅ Legacy URL redirects functioning correctly - ✅ Cache clearing and plugin activation working ## Benefits - Clean root directory with only essential development files - Preserved all legacy content in organized archive structure - Improved navigation and reduced clutter - Maintained full deployment functionality with updated paths 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
2.8 KiB
2.8 KiB
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
[... existing content remains unchanged ...]
Memory Entries
- Do not make standalone 'fixes' which upload separate from the plugin deployment. Instead, always redeploy the whole plugin with your fixes. Before deploying, always remove the old versions of the plugin. Always activate and verify after plugin upload
- Always use the deployment scripts to upload, activate and verify plugins for code changes
- The deployment process now automatically clears Breeze cache after plugin activation through wp-cli. This ensures proper cache invalidation and prevents stale content issues.
- Communication Templates system uses a modal interface with JavaScript override after wp_footer() to ensure external JS doesn't conflict. Scripts load on communication-templates page only.
- When testing the UI, use playwright + screenshots which you inspect personally to verify that your features are working as intended.
- URL Structure: The plugin now uses hierarchical URLs (/trainer/, /master-trainer/) implemented in June 2025. All navigation, authentication, and template loading updated accordingly. Backward compatibility maintained with 301 redirects.
- CSS Prevention System: ALWAYS run bin/pre-deployment-check.sh before any deployment. This prevents broken templates from reaching users. All templates MUST have get_header()/get_footer() calls.
- Deployment and Verification (2025-06-17): Use
scripts/deploy-to-staging.shfor deployments. Always runscripts/verify-plugin-fixes.shafter deployment. Plugin must be reactivated to create missing pages. Legacy redirects working at 100% success rate. Certificate reports 404 issue resolved. - Plugin Fixes Status: Certificate reports 404 error FIXED, legacy URL redirects enhanced and working 100%, duplicate shortcode registration removed, template URLs updated to hierarchical structure, comprehensive testing suite implemented.
- Master Dashboard CSS Fix (2025-06-18): Master dashboard CSS was broken due to missing get_header()/get_footer() calls in template. FIXED by adding WordPress integration, comprehensive CSS variables framework (--hvac-spacing-, --hvac-radius-), 200+ lines of master dashboard styles, proper AJAX handlers, and responsive design. Prevention system implemented with template validation scripts.
- Directory Reorganization (2025-06-18): Root directory reorganized for maintainability. Development artifacts moved to
archive/directory with structured subdirectories. Essential files (.env, core plugin files) restored to root. Deployment scripts moved toscripts/directory. Plugin redeployed successfully after reorganization - all functionality verified working.
[... rest of the existing content remains unchanged ...]