On this page test

This section is commonly called:

“Table of Contents (TOC)”

or more specifically for web docs/UI:

“On-page Table of Contents”

(also known as In-page Navigation)

Other names your dev might recognize:

• Page Anchor Navigation
• Sticky Sidebar TOC
• Jump Links / Anchor Links
• Section Navigator
• In-page Outline

How it usually works (for dev context):

• Auto-generated from headings (h2, h3, etc.)
• Uses anchor links (#section-id)
• Often sticky on scroll
• Highlights the active section while scrolling (scroll-spy)

👉 Best term to tell your dev:
“Add a sticky on-page Table of Contents (TOC) with anchor links”

If you want, I can:

• Give exact dev requirements (React / Next.js friendly)
• Share UX best practices (when to show/hide, mobile behavior)
• Provide a ready-to-use spec you can paste into Jira / Notion

give me only prompt so that dev can add this on blog view page like i mean when user can read blog then, and on the left side of blog page add other blogs name list

Prompt for dev:

Add a blog reading layout where the main blog content appears on the right, and a sticky left sidebar shows a list of other blog posts (title only).
The left sidebar should:

• Display other published blogs (excluding the current one)
• Be sticky on scroll (desktop only)
• Highlight the currently opened blog
• Be clickable links that navigate to selected blogs
• Collapse into a dropdown or hide completely on mobile

The layout should be clean, readable, and optimized for long-form content, without affecting page performance or SEO.