Add db_content_updates directory for production sync

- Create db_content_updates/ for documenting database changes
- Add README with required document format and template
- Update CLAUDE.md with mandatory documentation requirement
- All content changes must be documented for production team

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Hanson.xyz Dev
2026-01-04 20:12:05 -06:00
parent f0ca867605
commit 25608a5327
2 changed files with 84 additions and 5 deletions
+67
View File
@@ -0,0 +1,67 @@
# Database Content Updates
This directory contains documentation for all database content changes made in development that need to be applied to production.
## When to Create a Document
Create a document here whenever you make changes to:
- WordPress options (`wp_options` table)
- ACF field values (Theme Options, page fields, etc.)
- Posts, pages, or custom post type content
- Menus and menu items
- Taxonomy terms
- User meta or other wp_usermeta changes
## Document Format
**Filename**: `YYYY-MM-DD_HH-MM_short-description.md`
Example: `2026-01-04_19-30_add-properties-page.md`
**Required Sections**:
```markdown
# [Brief Title]
**Date**: YYYY-MM-DD HH:MM
**Author**: [Your name or "Claude"]
## Summary
One sentence describing what changed and why.
## Changes Made
### [Change 1 Title]
**Type**: [option | acf_field | post | menu | term | other]
**Table**: [wp_options | wp_postmeta | etc.]
**WP-CLI Command(s)**:
wp --allow-root [exact command here]
**Or SQL**:
[exact SQL here]
**Values Set**:
- field_name: "value"
- another_field: 123
### [Change 2 Title]
...
## Dependencies
- List any changes that must be applied first
- Or note "None" if standalone
## Verification
How to verify the change was applied correctly:
- Check URL: /some-page/
- Verify in admin: Settings > Theme Options > Tab Name
```
## Important Notes
1. Be EXACT - copy/paste actual commands and values
2. Include post IDs, option names, field keys - no ambiguity
3. If order matters, number the steps
4. Test your commands before documenting them
5. Production team will execute these verbatim