Hi@folz this would be an awesome example of a fairly simple docblock to write. I'm on the hook for documentingaddon-docs as part of the 6.0 milestone, so once there's a dev guide it would be amazing if you could kick the tires on that and see how hard it is to implement this. I'd expect it shouldn't be too hard to extract this information automatically and create the links.

For sure, that sounds good to me! Is there a place I can follow for updates to 6.0, or would you be able to tag me in this issue once that's released?

@folz absolutely. i'll tag you here when it's ready.

in terms of 6.0 here's a general issue (still basically empty):#9311

and for doc blocks documentation there isn't an issue yet. here's the closest thing to track#8379

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

Converting this to a discussion. We’re reserving feature issues for things that are on ourshort-term roadmap. We’ll check back periodically to see whether this is a good candidate to be added. If this feature would be useful to you, please upvote!

This would be an excellent feature to add. We have implemented it in our codebase in a hacky way but a proper official DocBlock for it would be great.

Until we get a proper block for this basic feature, here's a block you can place in your MDX files. Might have to tweak it some for your setup or Storybook version (I'm on version 8). Tried usingitems.json initially and figuring out using API but it was a bit overwhelming... sometimes it's just easier to work off rendered content in the sidebar.

exportconstFooter=({  nextLink,  prevLink,  nextLinkText,  prevLinkText}:{nextLink:string;prevLink:string;nextLinkText:string;prevLinkText:string;})=>{varfindAdjacentSibling=function(elem,selector,direction:'prev'|'next'){// Get the next sibling elementvarsibling=elem[direction==='prev' ?'previousElementSibling' :'nextElementSibling'];if(!selector)returnsibling;while(sibling){if(sibling.matches(selector))returnsibling;sibling=sibling[direction==='prev' ?'previousElementSibling' :'nextElementSibling'];}};constgetAdjacentPageInSidebar=(direction:'prev'|'next')=>{// From parent iframeconstsidebar=window.parent.document.querySelector('#storybook-explorer-tree');if(!sidebar)returnnull;constsidebarActiveItem=sidebar.querySelector('[data-selected="true"]');if(!sidebarActiveItem)returnnull;constsidebarAdjacentToActiveItem=findAdjacentSibling(sidebarActiveItem,'.sidebar-item',direction);if(!sidebarAdjacentToActiveItem)returnnull;constsidebarAdjacentToActiveItemLink=sidebarAdjacentToActiveItem.querySelector('a');if(!sidebarAdjacentToActiveItemLink)returnnull;console.log(sidebarAdjacentToActiveItemLink.getAttribute('href'));returnsidebarAdjacentToActiveItemLink;};constprevDocLink=getAdjacentPageInSidebar('prev');constnextDocLink=getAdjacentPageInSidebar('next');constprevDocLinkText=prevDocLink?.textContent;constnextDocLinkText=nextDocLink?.textContent;constprevDocLinkHref=prevDocLink?.getAttribute('href');constnextDocLinkHref=nextDocLink?.getAttribute('href');return(<>{(prevLink||prevDocLinkHref)&&(<ahref={prevLink??prevDocLinkHref}>{prevLinkText||prevDocLinkText}</a>)}{(nextLink||nextDocLinkHref)&&(<ahref={nextLink??nextDocLinkHref}>{nextLinkText||nextDocLinkText}</a>)}</>);};

Then at the bottom of your MDX you would do<Footer />