# WordPress Template Validation Guide

## MANDATORY TEMPLATE STRUCTURE

Every WordPress template MUST follow this exact structure:

```php
<?php
/**
 * Template Name: [Template Name]
 */

// Security check
if (!defined('ABSPATH')) {
    exit;
}

// Auth and permission checks here...

// CRITICAL: Always call get_header()
get_header();
?>

<div id="primary" class="content-area primary ast-container">
    <main id="main" class="site-main">
        
        <!-- Your template content here -->
        
    </main>
</div>

<?php
// CRITICAL: Always call get_footer()
get_footer();
?>
```

## VALIDATION CHECKLIST

Before any template goes live:

- [ ] `get_header()` called at template start
- [ ] `get_footer()` called at template end  
- [ ] Proper WordPress container structure
- [ ] Security check with `ABSPATH`
- [ ] Permission checks for protected pages
- [ ] CSS classes match existing framework
- [ ] AJAX handlers use proper WordPress hooks

## COMMON MISTAKES TO AVOID

1. **Missing header/footer calls** - Breaks all CSS loading
2. **Inline AJAX instead of wp_ajax hooks** - Security issues
3. **Hardcoded URLs** - Breaks on different environments
4. **Missing nonce verification** - Security vulnerabilities
5. **Custom CSS classes without corresponding CSS** - Broken styling

## TESTING REQUIREMENTS

Every template must pass:
- [ ] Visual test with screenshots
- [ ] CSS loading verification
- [ ] AJAX functionality test
- [ ] Mobile responsiveness check
- [ ] Authentication flow test