🔍 Preview links for changed docs

• docs/configure/content-set/navigation.md

@bmorelli25 See the GitHub repository link in https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/1613/configure/content-set/navigation

oooooh I immediately want to use this to add a link to the Elasticsearch reference docs in the Elasticsearch solution nav 😍

would this be a valid use case?

would this be a valid use case?

There's a thread in #elastic-docs-v3 about this. There are two use cases and that's the other one. Not sure if Fabri is also working on that 🧙

@Mpdreamz @bmorelli25 After melting Claude's brain, it looks like adding crosslinks validation and rendering to the toc is too much. LLMs being unable to figure this out suggests that crosslinks depend deeply on the overall architecture, but correct me if I'm wrong.

For a quick solution, I'd rather show external links as they appear now and, if they start with elastic.co/docs, open them as if they were normal toc links (no icon, no _blank target). How does that sound?

I am going to mull over this one over the weekend. For sure I don't want links to elastic.co/docs using this mechanism that should result in an error.

We could support:

link: docs-content://a/b/c.md

The styling of navigation items has changed as part of this PR.

@Mpdreamz I love that. Any hint on how to achieve that though? I mean the crosslinks in the toc.

You need the current ICrossLinkUrlResolver, I think it's best to to this in two phases.

After Tree is build iterate over it to validate all cross links.

We already do something similar to ensure the validity of navigation index:

CSS issue solved for this particular PR, @Mpdreamz! We shouldn't abuse this system though, I agree.

We can probably close this one if #1615 gets merged, though it'd be a separate functionality.

Closing this in favor of #1615