- Added image optimization with WebP conversion
- Updated Dashboard UI with card layout
- Fixed duplicate domain/email detection
- Increased default items per page to 25
- Added campaign weekend reduction factor field
- Added ember animation effect in footer
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
32 lines
No EOL
1.3 KiB
Markdown
32 lines
No EOL
1.3 KiB
Markdown
# Mailferno WordPress Theme - Development Guidelines
|
|
|
|
## Development Environment
|
|
- This is a WordPress theme that appears to be a child theme of GeneratePress
|
|
- Project includes custom templates for a SaaS email service (Mailferno)
|
|
- WordPress core functions and AJAX are used extensively
|
|
|
|
## Code Style Guidelines
|
|
- Indentation: 4 spaces (not tabs)
|
|
- Function/variable naming: snake_case (e.g., my_function_name)
|
|
- Constants/globals: UPPERCASE_WITH_UNDERSCORES
|
|
- Opening braces on separate lines for functions and control structures
|
|
- Add spaces after control keywords (if, for, while)
|
|
|
|
## WordPress Patterns
|
|
- Use WordPress coding standards for hook naming
|
|
- Prefix custom functions with theme prefix to avoid conflicts
|
|
- Use WordPress sanitization functions for user input
|
|
- Validate data with WordPress validation functions
|
|
- Follow WordPress nonce verification practices for forms
|
|
|
|
## Error Handling
|
|
- Use try/catch blocks for operations that may fail
|
|
- Check return values with is_wp_error() for WP operations
|
|
- Return early from functions when conditions aren't met
|
|
- Use log_to_file() for debug logging
|
|
|
|
## Common Tasks
|
|
- Testing: Manual testing in WordPress admin and frontend
|
|
- Development: Use WP_DEBUG=true in wp-config.php for development
|
|
- Code organization: Group related functions together
|
|
- JavaScript: Include at bottom of template files or enqueue properly |