Skip to content

feat(special): add browsable Special:LonelyPages report page#1969

Closed
carlh7777 wants to merge 1 commit into
e35ventura:testfrom
carlh7777:feat/special-lonelypages-page
Closed

feat(special): add browsable Special:LonelyPages report page#1969
carlh7777 wants to merge 1 commit into
e35ventura:testfrom
carlh7777:feat/special-lonelypages-page

Conversation

@carlh7777

Copy link
Copy Markdown

Summary

  • Add a browsable /wiki/special/lonelypages/ page for the orphaned-articles report that previously only existed as lonelypages.json, mirroring the Special:WantedPages HTML page (feat(special): add Special:WantedPages report page #1953)
  • LonelyPages is the direct complement of Special:MostLinkedPages, which already has an HTML page
  • Render the report from the same shared buildLonelyPages builder over the same public/data/backlinks.json the JSON endpoint reads, so the HTML page and JSON companion stay in lockstep
  • Register the route in the sitemap and share-preview metadata (drives /og/special/lonelypages.png share card)
  • Extend check-lonely-pages.js and check-sitemap.js to assert the HTML route

Test plan

  • Run npm run build and confirm /wiki/special/lonelypages/ renders with the expected heading and article list
  • Verify each listed orphan links to its article page and backlinks page
  • Confirm empty state copy when there are no lonely pages
  • Run node scripts/check-lonely-pages.js — passes with HTML route aligned
  • Run node scripts/check-sitemap.js — sitemap includes /wiki/special/lonelypages/
  • Confirm share preview / OG card metadata for lonelypages is present

Add a browsable `/wiki/special/lonelypages/` page for the orphaned-articles
report that previously only existed as `lonelypages.json`, mirroring the
Special:WantedPages HTML page (e35ventura#1953). LonelyPages is the direct complement of
Special:MostLinkedPages, which already has an HTML page.

- render the report from the same shared `buildLonelyPages` builder over the
  same `public/data/backlinks.json` the JSON endpoint reads, so the HTML page
  and JSON companion stay in lockstep
- register the route in the sitemap and share-preview metadata (the latter
  drives the `/og/special/lonelypages.png` share card, keeping the bidirectional
  special-page ↔ OG-card invariant satisfied)
- extend check-lonely-pages.js and check-sitemap.js to assert the HTML route

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@carlh7777
carlh7777 requested a review from e35ventura as a code owner July 2, 2026 17:44
@taopedia-site-maintainer taopedia-site-maintainer Bot added feature Website feature or behavior request ui-ux Visual design, layout, or usability work labels Jul 2, 2026
@taopedia-site-maintainer

Copy link
Copy Markdown

Verdict: Close

PR #1969: feat(special): add browsable Special:LonelyPages report page

This PR changes UI, layout, styling, responsive behavior, or interaction behavior, but the PR description does not clearly include before/after author-provided screenshots or a short screen recording.

Visual PRs need evidence in the PR description so the maintainer can review the change quickly and reliably. A deploy preview link alone is not enough.

Required evidence for resubmission:

  • Page URL.
  • Viewport width, especially for responsive changes.
  • Action taken, for interaction changes.
  • Expected before behavior.
  • Expected after behavior.
  • Screenshots for static visual changes, or a short video/GIF for interaction changes.

Changed files:

  • scripts/check-lonely-pages.js
  • scripts/check-sitemap.js
  • src/lib/share-preview.ts
  • src/pages/sitemap.xml.ts
  • src/pages/wiki/special/lonelypages.astro

CI: No visible GitHub checks yet.

Please open a new focused PR with the required evidence attached.


Automated review by Taopedia Site Maintainer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature Website feature or behavior request ui-ux Visual design, layout, or usability work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant