Skip to content

[DOCS] Remove screenshot placeholders #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
N0S0I merged 1 commit into from
Sep 1, 2026
Merged

[DOCS] Remove screenshot placeholders #7

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 0 additions & 12 deletions Documentation/Commands/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
--------------------------

Expand Down Expand Up @@ -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.
12 changes: 0 additions & 12 deletions Documentation/Configuration/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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``

Expand All @@ -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``
Expand Down
6 changes: 0 additions & 6 deletions Documentation/Requirements/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
24 changes: 0 additions & 24 deletions Documentation/VerifySetup/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
===============

Expand Down Expand Up @@ -84,24 +78,6 @@ Open the Sentry project and verify these results:
- An issue alert named ``Monitor Alert for <normalized task
title>-uid-<task 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.

Expand Down