Notes & Activities API Content Cleanup Summary

Overview #

Removed all API endpoints, CRUD operations, code examples, and technical implementation details from the Notes and Activities user guide files while preserving UI instructions and user-friendly content.

Files Cleaned (6 total) #

1. adding-notes.md

• ✅ Status: Clean – No API content found
• Content: UI instructions for adding notes, note examples (user content, not code), best practices
• Preserved: All user-facing instructions and note content examples

2. deleting-notes.md

• ✅ Removed: API deletion endpoint with curl example
• Preserved: WordPress Admin UI deletion steps, permissions explanation, data recovery options
• Changes: Removed “Via API” section with DELETE endpoint

3. editing-notes.md

• ✅ Removed: API update endpoint with curl example
• Preserved: Contact edit screen UI instructions, editable fields, best practices
• Changes: Removed “Via API” section with PUT endpoint, kept “Via Contact Edit Screen” as main section

4. note-permissions.md

• ✅ Removed:
  • API endpoint documentation (GET, POST, PUT, DELETE)
  • API permission enforcement section
  • curl example for role creation
  • JSON error response examples
• Preserved:
  • Role Manager UI instructions
  • Permission levels explanation
  • Role examples
  • Common scenarios
  • User-friendly troubleshooting
• Changes:
  • Removed “Via API” subsection under “Configuring Permissions”
  • Removed entire “API Enforcement” section
  • Simplified “Permissions + Contact Ownership” example (removed code block formatting)

5. note-types-explained.md

• ✅ Removed: API filtering curl example
• Preserved: Note type descriptions, UI filtering instructions, best practices
• Changes: Removed “API Filtering” subsection under “Filtering by Type”

6. viewing-contact-timeline.md

• ✅ Removed:
  • API endpoint for fetching notes
  • API filtering examples (by type and date range)
• Preserved:
  • WordPress Admin and Mobile App access instructions
  • Timeline display information
  • Best practices for different teams
• Changes:
  • Removed “Via API” subsection under “Accessing the Timeline”
  • Replaced detailed API filtering section with simple user-friendly description

Summary of Removals #

API Endpoints Removed:

• GET /wp-json/plover-crm/v1/contacts/{id}/notes (with pagination)
• GET /wp-json/plover-crm/v1/contacts/{id}/notes?type=call (filtering)
• GET /wp-json/plover-crm/v1/contacts/{id}/notes?start_date=...&end_date=... (date range)
• POST /wp-json/plover-crm/v1/contacts/{id}/notes (create)
• PUT /wp-json/plover-crm/v1/notes/{id} (update)
• DELETE /wp-json/plover-crm/v1/notes/{id} (delete)
• POST /wp-json/plover-crm/v1/roles (role creation)

Code Examples Removed:

• 8 curl command examples
• 1 JSON request body example (role creation)
• 1 JSON error response example

Technical Content Removed:

• API authentication headers
• HTTP methods and status codes
• JSON request/response structures
• API permission enforcement details

Content Preserved #

UI Instructions:

• ✅ How to add notes via WordPress Admin
• ✅ How to edit notes via Contact Edit Screen
• ✅ How to delete notes via WordPress Admin
• ✅ How to configure permissions via Role Manager
• ✅ How to filter timeline by type
• ✅ How to access timeline (WordPress Admin & Mobile App)

User-Friendly Content:

• ✅ Note type descriptions and examples
• ✅ Permission levels explanation
• ✅ Role examples (Super Admin, Sales Rep, etc.)
• ✅ Best practices for each workflow
• ✅ Common scenarios and use cases
• ✅ Troubleshooting tips
• ✅ Team collaboration examples

Result #

All 6 files now contain only user-facing documentation focused on UI interactions, with no API endpoints, technical implementation details, or code examples. The documentation is now appropriate for end-users who interact with PloverCRM through the WordPress admin interface.

---

Cleanup completed: February 3, 2026