Remove emojis from all markdown docs, add consolidation plan

- Strip emojis from 47 markdown files across docs/, sql/, and root
- Add docs/DOCS_CONSOLIDATION_PLAN.md with plan to reduce 45 docs to 8
- Establish no-emoji rule for documentation going forward

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
cproudlock
2025-12-11 07:42:52 -05:00
parent 9fc3420716
commit e598f72616
42 changed files with 1105 additions and 937 deletions

View File

@@ -454,14 +454,14 @@ SET SQL_SAFE_UPDATES = 1;
| Feature | Old (fields on machines) | New (warranty tables) |
|---------|-------------------------|----------------------|
| Multiple warranties | No | Yes |
| Warranty history | No | Yes |
| Renewal tracking | No | Yes |
| Cost tracking | No | Yes |
| Different vendors | No | Yes |
| Auto-notifications | No | Yes |
| Reporting | ⚠️ Limited | Comprehensive |
| Audit trail | No | Yes |
| Multiple warranties | No | Yes |
| Warranty history | No | Yes |
| Renewal tracking | No | Yes |
| Cost tracking | No | Yes |
| Different vendors | No | Yes |
| Auto-notifications | No | Yes |
| Reporting | Limited | Comprehensive |
| Audit trail | No | Yes |
### 6.2 Example Use Cases
@@ -502,12 +502,12 @@ The machines table should NOT have warranty fields. All warranty information wil
## Next Steps
1. Review warranty table design
2. Create warranty management views
3. Create data migration script for PC warranties
4. Update PC migration plan to use warranty tables
5. Create ASP pages for warranty management
6. Create warranty expiration notification system
1. Review warranty table design
2. Create warranty management views
3. Create data migration script for PC warranties
4. Update PC migration plan to use warranty tables
5. Create ASP pages for warranty management
6. Create warranty expiration notification system
---