Problem Statement: Currently, webhooks only fire when specific article events occur (publish, unpublish, delete, etc.). Users have no way to manually trigger a webhook event for testing, debugging failed integrations, or resynchronizing external systems after a disconnection. The only option is to change article state, which may not be appropriate or desired. Suggested Enhancement: Add a "Test Webhook" or "Trigger Event" button in the article editor that allows users to manually fire configured webhook events for the current article without changing article state or visibility. Customer Benefit: Improves debugging and troubleshooting of webhook integrations Enables recovery workflows when external systems miss or fail to process events Reduces support tickets related to webhook synchronization issues Provides better developer experience during integration setup