Skip to content

Update Domain Monitor docs and Advanced Uptime Monitor nav label - #57

Merged
bkatusic merged 2 commits into
mainfrom
docs-review/mainwp-domain-monitor-extension
May 26, 2026
Merged

bkatusic merged 2 commits into
mainfrom
docs-review/mainwp-domain-monitor-extension

Conversation

@bkatusic

@bkatusic bkatusic commented May 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Updated the Advanced Uptime Monitor sidebar label to match the full product name.
  • Refined the Domain Monitor page to use current navigation labels, fresh version metadata, and source-backed workflow wording.
  • Replaced the inline TLD list with maintained external references and kept the RDAP-first explanation.
  • Pointed the REST API section to the MainWP Postman workspace as the canonical up-to-date reference.

Testing

  • Not run (not requested).

Summary by CodeRabbit

Documentation

  • Updated Advanced Uptime Monitor extension documentation with revised extension naming metadata
  • Enhanced Domain Monitor extension documentation to version 5.1.5 with refined TLD lookup guidance including RDAP/WHOIS references, expanded WP CLI command examples for checking individual and multiple sites with result retrieval, updated navigation paths, and improved available reports tokens formatting

Review Change Stack

@coderabbitai

coderabbitai Bot commented May 26, 2026

Copy link
Copy Markdown

Walkthrough

Updated 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.

Changes

Monitoring Extensions Documentation

Layer / File(s) Summary
Advanced Uptime Monitor sidebar title
add-ons/monitoring/advanced-uptime-monitor-extension.mdx
Updated the sidebarTitle metadata from "Uptime Monitor" to "Advanced Uptime Monitor" for consistency with the extension name.
Domain Monitor version and TLD guidance
add-ons/monitoring/mainwp-domain-monitor-extension.mdx
Bumped extension version to 5.1.5 and replaced the static TLD list with an explanation of RDAP-first lookup behavior, WHOIS fallback, and references to IANA-maintained RDAP/registry sources, while retaining the manual entry option.
Domain Monitor navigation and instruction updates
add-ons/monitoring/mainwp-domain-monitor-extension.mdx
Updated navigation path labels across all domain check workflows (Check Domains, Manual Entry, Domain Info, Automated Checks) to use the consistent "Add-ons > Monitoring > Domain Monitor" structure; reworded step instructions and menu action labels.
Domain Monitor WP CLI and token documentation
add-ons/monitoring/mainwp-domain-monitor-extension.mdx
Expanded "Check Sites via WP CLI" section with example commands for checking specific sites, multiple sites, and all sites, plus result retrieval; reformatted "Available Reports Tokens" from prose into a clearer bullet-list of token keys with updated descriptions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • mainwp/docs#56: Modifies the same advanced-uptime-monitor-extension.mdx file; updates Advanced Uptime Monitor metadata and documentation flows that may overlap with this PR's sidebar title change.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and clearly summarizes both main changes: updating Domain Monitor documentation and updating the Advanced Uptime Monitor navigation label.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs-review/mainwp-domain-monitor-extension

Comment @coderabbitai help to get the list of available commands and usage tips.

@mintlify

mintlify Bot commented May 26, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
mainwp 🟢 Ready View Preview May 26, 2026, 1:37 PM

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between fcb23f9 and adcab9e.

📒 Files selected for processing (2)
  • add-ons/monitoring/advanced-uptime-monitor-extension.mdx
  • add-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)**.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

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.

Suggested change
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. ![Screenshot showing Manual Domain information entry toggle in settings](/images/add-ons/domain-monitor-widget.png)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

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. ![Screenshot showing Manual Domain information entry toggle in settings](/images/add-ons/domain-monitor-widget.png)
+If your domain information cannot be retrieved automatically via RDAP/WHOIS, you can add it manually by following the steps below. ![Screenshot showing Manual Domain information entry toggle in settings](/images/add-ons/domain-monitor-widget.png)
📝 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.

Suggested change
If your domain is not on the list of supported TLDs, you can add information manually by following the steps below. ![Screenshot showing Manual Domain information entry toggle in settings](/images/add-ons/domain-monitor-widget.png)
If your domain information cannot be retrieved automatically via RDAP/WHOIS, you can add it manually by following the steps below. ![Screenshot showing Manual Domain information entry toggle in settings](/images/add-ons/domain-monitor-widget.png)
🤖 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.

@bkatusic
bkatusic merged commit f57851f into main May 26, 2026
5 checks passed
@bkatusic
bkatusic deleted the docs-review/mainwp-domain-monitor-extension branch May 26, 2026 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant