Skip to content

[P1] Add 'Related Pages' Content Recommendations at Bottom of Each Page #178

Description

@flexykrn

Bug Description

Users reaching the end of a documentation page encounter a dead end with no guidance on what to read next. This increases bounce rate and reduces content discovery. Competitors use 'Related Pages' or 'You May Also Like' sections to keep users engaged and guide their learning journey.

Competitor Benchmark

  • Ethereum: 'Related tutorials' section at bottom of guides
  • Solana: 'Next Steps' with 3 related pages per article
  • Stripe Docs: 'Related' sidebar with contextual recommendations
  • Vercel: 'On this page' + 'Related' dual navigation

Affected Pages

  • All tutorial and guide pages (50+ pages)
  • High-impact pages:
    • /build/smart-contracts/ tutorials
    • /xdcchain/developers/ guides
    • /enterprise/ integration docs
    • /subnet/ setup guides

Blast Radius

  • Primary: New developers learning XDC
  • Secondary: Returning users exploring advanced topics
  • Impact: Reduced bounce rate, increased time-on-site, better onboarding flow

Root Cause Analysis

Content is siloed. No taxonomy or tagging system connects related topics. The existing #130 (cross-links) adds manual inline links but does not provide automated discovery at end-of-page.

Proposed Solution

Option A: Manual Related Pages (Recommended for immediate fix)

Add related_pages to YAML frontmatter:

---
related_pages:
  - /build/smart-contracts/deployment
  - /learn/token-standards
  - /xdcchain/developers/tools
---

Render as cards at bottom of page.

Option B: Tag-Based Auto-Recommendation

Add tags to pages, auto-suggest based on shared tags.

Additional Fixes Required

  • Design related page card component (title + 1-line description + icon)
  • Add to page template
  • Populate frontmatter for top 20 most-visited pages first
  • Mobile responsive grid layout

Acceptance Criteria

  • Every tutorial/guide page shows 3 related pages at bottom
  • Related pages are contextually relevant (not random)
  • Cards show page title + description preview
  • Clickable with hover state
  • Mobile: stacked vertically, not horizontal grid

Raw Context

A developer finishing 'Hello World' contract has no guidance on what to learn next (token standards? deployment? testing?). They leave instead of continuing their journey.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions