From 57f11b42947049ae28053f490df1608365ece9d9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Itay=20Kr=C3=A4mer?= Date: Tue, 1 Sep 2026 13:55:06 +0200 Subject: [PATCH] [DOCS] Remove screenshot placeholders --- Documentation/Commands/Index.rst | 12 ------------ Documentation/Configuration/Index.rst | 12 ------------ Documentation/Requirements/Index.rst | 6 ------ Documentation/VerifySetup/Index.rst | 24 ------------------------ 4 files changed, 54 deletions(-) diff --git a/Documentation/Commands/Index.rst b/Documentation/Commands/Index.rst index 58d52c9..b2943cb 100644 --- a/Documentation/Commands/Index.rst +++ b/Documentation/Commands/Index.rst @@ -35,12 +35,6 @@ Run the command without options first: The command lists the ID, slug, and name of every matching monitor but deletes nothing. -.. admonition:: SCREENSHOT TODO: Muted monitor cleanup preview - - Add :file:`Documentation/Images/DeleteMutedMonitorsPreview.png`. Show the - command table with example monitors. Use artificial names and redact IDs - from a real Sentry organization. - Delete the listed monitors -------------------------- @@ -70,9 +64,3 @@ To run cleanup on a schedule: Automatic cleanup permanently deletes every muted monitor in the configured project. Use the preview command after configuration changes and before enabling the scheduled task. - -.. admonition:: SCREENSHOT TODO: Automatic muted monitor cleanup - - Add :file:`Documentation/Images/Typo3DeleteMutedMonitorsTask.png`. Show the - TYPO3 Scheduler task with the selected command, ``--force`` option, and - schedule. Do not include customer-specific task data. diff --git a/Documentation/Configuration/Index.rst b/Documentation/Configuration/Index.rst index 4c25f86..d6fd193 100644 --- a/Documentation/Configuration/Index.rst +++ b/Documentation/Configuration/Index.rst @@ -66,12 +66,6 @@ Configuration reference Numeric integration ID from the target URL of the :guilabel:`Configure` link in the Sentry Microsoft Teams integration. - .. admonition:: SCREENSHOT TODO: Microsoft Teams integration ID - - Add :file:`Documentation/Images/SentryTeamsIntegrationId.png`. Show the - Sentry integration overview and the :guilabel:`Configure` link used to - find the numeric integration ID. Redact organization-specific values. - ``orgName`` Environment variable: ``SENTRY_ORGANIZATION`` @@ -91,12 +85,6 @@ Configuration reference permissions. The extension uses it to manage issue alert rules and to list and delete cron monitors. - .. admonition:: SCREENSHOT TODO: Sentry authentication token permissions - - Add :file:`Documentation/Images/SentryAuthTokenPermissions.png`. Show - the required alert-rule permissions without displaying the token value, - user email address, or organization details. - .. _configuration-timezone: ``timezone`` diff --git a/Documentation/Requirements/Index.rst b/Documentation/Requirements/Index.rst index 5c22167..21785a3 100644 --- a/Documentation/Requirements/Index.rst +++ b/Documentation/Requirements/Index.rst @@ -24,12 +24,6 @@ Sentry requirements permissions to manage issue alert rules and cron monitors * Outbound HTTPS access from TYPO3 to the Sentry host -.. admonition:: SCREENSHOT TODO: Sentry project and DSN - - Add :file:`Documentation/Images/SentryProjectDsn.png`. Show where an - integrator finds the project DSN in Sentry. Redact the public key, secret - values, organization details, and project identifiers. - .. important:: This extension depends on an initialized Sentry SDK but does not initialize diff --git a/Documentation/VerifySetup/Index.rst b/Documentation/VerifySetup/Index.rst index 2649f12..1cf9557 100644 --- a/Documentation/VerifySetup/Index.rst +++ b/Documentation/VerifySetup/Index.rst @@ -32,12 +32,6 @@ List the configured Scheduler tasks: Record the UID of a harmless task. -.. admonition:: SCREENSHOT TODO: TYPO3 Scheduler task list - - Add :file:`Documentation/Images/Typo3SchedulerTaskList.png`. Show the TYPO3 - Scheduler backend module with one harmless task, its UID, schedule, and - manual execution action visible. Do not include customer data. - 2. Run the task =============== @@ -84,24 +78,6 @@ Open the Sentry project and verify these results: - An issue alert named ``Monitor Alert for -uid-`` exists. -.. admonition:: SCREENSHOT TODO: Sentry cron monitor overview - - Add :file:`Documentation/Images/SentryCronMonitorOverview.png`. Show the - Sentry :guilabel:`Crons` overview with the newly created TYPO3 task monitor - and a healthy status. - -.. admonition:: SCREENSHOT TODO: Successful Sentry check-in - - Add :file:`Documentation/Images/SentryCronMonitorDetails.png`. Show the - monitor detail page with the expected schedule and the latest ``ok`` - check-in. Redact project and organization details where necessary. - -.. admonition:: SCREENSHOT TODO: Generated Sentry alert rule - - Add :file:`Documentation/Images/SentryIssueAlertRule.png`. Show the generated - issue alert rule, its ``monitor.slug`` filter, ``Production`` environment, - and Microsoft Teams action. - The first execution creates the monitor and issue alert. Later executions reuse the matching alert rule.