export declare const inlineLinksExample = "\nJSDoc/TSDoc `{@link Target}` references inside component descriptions are\nturned into clickable links \u2014 the same syntax IDEs use for cmd-click\nnavigation. The plugin recognises:\n\n- A known component tag: {@link kompendium-markdown}\n- A known type: {@link MenuItem}\n- A pipe-delimited display label: {@link MenuItem | the menu item interface}\n- A space-delimited display label: {@link MenuItem the menu item interface}\n- An absolute URL: {@link https://example.com | external resource}\n\nIdentifiers the resolver does not recognise still get rendered as inline\ncode, so they remain visually distinct from prose even when there is\nnothing to navigate to:\n\n- Unknown identifier: {@link DoesNotExist}\n- Unknown identifier with a free-form label: {@link DoesNotExist a missing type}\n\nReferences inside inline code such as `{@link MenuItem}` are intentionally\nleft untouched, so the literal syntax can be shown in documentation about\nthe feature itself.\n\n```ts\n// References inside fenced code blocks are left alone too:\n// {@link MenuItem} stays exactly like this.\n```\n";