Update Domain Monitor docs and Advanced Uptime Monitor nav label - #57
Conversation
WalkthroughUpdated Advanced Uptime Monitor sidebar title to match the extension name. Revised Domain Monitor documentation for version 5.1.5, replacing the TLD list with RDAP/WHOIS lookup guidance, modernized navigation paths throughout UI instructions, and expanded WP CLI examples with reformatted token documentation. ChangesMonitoring Extensions Documentation
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@add-ons/monitoring/mainwp-domain-monitor-extension.mdx`:
- Line 59: The link pointing to `#manual-entry` is broken because the actual
heading is "Enter Domain Info Manually"; either update the in-page anchor in the
link to match the heading (e.g., use `#enter-domain-info-manually`) or add an
explicit id attribute to the heading (e.g., add an HTML id or MDX/Markdown
anchor named `manual-entry`) so the link target exists; update the link text or
heading id consistently to ensure the anchor jump works (refer to the link
`#manual-entry` and the heading "Enter Domain Info Manually" when making the
change).
- Line 104: Replace the stale phrase "not on the list of supported TLDs" in the
sentence containing that exact text with wording that reflects the new
RDAP/WHOIS guidance model (for example: "cannot be resolved via RDAP/WHOIS" or
"is not supported by RDAP/WHOIS lookup"); update the sentence in
add-ons/monitoring/mainwp-domain-monitor-extension.mdx that currently reads "If
your domain is not on the list of supported TLDs, you can add information
manually..." to use the new phrasing so it no longer references a removed inline
TLD list and instead points readers to the RDAP/WHOIS guidance model.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 72fc680c-1892-4cb7-bff1-86fd58c23951
📒 Files selected for processing (2)
add-ons/monitoring/advanced-uptime-monitor-extension.mdxadd-ons/monitoring/mainwp-domain-monitor-extension.mdx
| - [IANA RDAP DNS bootstrap data](https://data.iana.org/rdap/dns.json) - Current RDAP service coverage by TLD. | ||
| - [IANA Root Zone Database](https://www.iana.org/domains/root/db) - Current TLD registry records, including WHOIS server details where available. | ||
|
|
||
| If the extension cannot retrieve your domain information automatically, you can enter it manually as described **[below](/add-ons/monitoring/mainwp-domain-monitor-extension#manual-entry)**. |
There was a problem hiding this comment.
Fix broken in-page anchor for manual entry section.
Line 59 links to #manual-entry, but that anchor does not exist for the current heading (Enter Domain Info Manually), so the jump target is broken.
Suggested fix
-If the extension cannot retrieve your domain information automatically, you can enter it manually as described **[below](/add-ons/monitoring/mainwp-domain-monitor-extension#manual-entry)**.
+If the extension cannot retrieve your domain information automatically, you can enter it manually as described **[below](/add-ons/monitoring/mainwp-domain-monitor-extension#enter-domain-info-manually)**.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| If the extension cannot retrieve your domain information automatically, you can enter it manually as described **[below](/add-ons/monitoring/mainwp-domain-monitor-extension#manual-entry)**. | |
| If the extension cannot retrieve your domain information automatically, you can enter it manually as described **[below](/add-ons/monitoring/mainwp-domain-monitor-extension#enter-domain-info-manually)**. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@add-ons/monitoring/mainwp-domain-monitor-extension.mdx` at line 59, The link
pointing to `#manual-entry` is broken because the actual heading is "Enter
Domain Info Manually"; either update the in-page anchor in the link to match the
heading (e.g., use `#enter-domain-info-manually`) or add an explicit id
attribute to the heading (e.g., add an HTML id or MDX/Markdown anchor named
`manual-entry`) so the link target exists; update the link text or heading id
consistently to ensure the anchor jump works (refer to the link `#manual-entry`
and the heading "Enter Domain Info Manually" when making the change).
|
|
||
| ## Enter Domain Info Manually | ||
|
|
||
| If your domain is not on the list of supported TLDs, you can add information manually by following the steps below.  |
There was a problem hiding this comment.
Update stale wording that still refers to a removed supported-TLD list.
Line 104 says “not on the list of supported TLDs,” but this PR removed the inline list. Reword to match the new RDAP/WHOIS guidance model.
Suggested fix
-If your domain is not on the list of supported TLDs, you can add information manually by following the steps below. 
+If your domain information cannot be retrieved automatically via RDAP/WHOIS, you can add it manually by following the steps below. 📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| If your domain is not on the list of supported TLDs, you can add information manually by following the steps below.  | |
| If your domain information cannot be retrieved automatically via RDAP/WHOIS, you can add it manually by following the steps below.  |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@add-ons/monitoring/mainwp-domain-monitor-extension.mdx` at line 104, Replace
the stale phrase "not on the list of supported TLDs" in the sentence containing
that exact text with wording that reflects the new RDAP/WHOIS guidance model
(for example: "cannot be resolved via RDAP/WHOIS" or "is not supported by
RDAP/WHOIS lookup"); update the sentence in
add-ons/monitoring/mainwp-domain-monitor-extension.mdx that currently reads "If
your domain is not on the list of supported TLDs, you can add information
manually..." to use the new phrasing so it no longer references a removed inline
TLD list and instead points readers to the RDAP/WHOIS guidance model.
Summary
Testing
Summary by CodeRabbit
Documentation