# Date Helper for Documentation

## Always Use Current Date

**CRITICAL:** Always detect and use the current date when creating or updating documentation. Never hardcode dates or assume dates.

## Quick Date Detection Commands

### Get Current Date (for documentation headers)

```bash
date +"%B %Y"        # Output: "November 2025"
date +"%Y-%m-%d"     # Output: "2025-11-19"
date +"%B %d, %Y"    # Output: "November 19, 2025"
```

### In PHP (for code)

```php
date('Y-m-d')                    // 2025-11-19
date('F Y')                      // November 2025
date('Y-m-d\TH:i:s\Z')          // 2025-11-19T12:00:00Z (ISO format)
```

### In Python (for scripts)

```python
from datetime import datetime
datetime.now().strftime("%B %Y")      # "November 2025"
datetime.now().strftime("%Y-%m-%d")   # "2025-11-19"
```

## Best Practices

1. **Always run date command** before updating documentation dates
2. **Use relative dates** when possible ("Last updated: [run date command]")
3. **Never assume** what month/year it is
4. **Update dates** when modifying existing documentation
5. **Use ISO format** (YYYY-MM-DD) for consistency

## Common Date Patterns

### Documentation Headers

```markdown
**Date:** November 2025
**Last Updated:** November 19, 2025
**Generated:** 2025-11-19
```

### Code Comments

```php
// Updated: 2025-11-19
// Last modified: November 2025
```

### Schema Dates

```json
{
  "datePublished": "2025-11-19T00:00:00+01:00",
  "dateModified": "2025-11-19T00:00:00+01:00"
}
```

## Quick Reference

**Current Date Detection:**

```bash
# Run this before updating any dates:
date +"%B %Y" && date +"%Y-%m-%d"
```

**Output Example:**

```
November 2025
2025-11-19
```

Use these values in your documentation!