R
Rich Rein
Several of my existing issues/feature requests share a similar theme - customize the rendered output of elements that currently allow markdown via domain-specific extensions (beyond/in addition to basic Markdown syntax)
Examples of what I believe to be related feature requests:
We had also raised an issue about the difference in rendering experience/timing between clicking a link in the menu on the catalog page versus examples of relative links like those found in the "Catalog Quick Access" section of the demo homepage.
Using the subset of Markdown (plus some Azure-specific additions) that is supported within Azure DevOps as an example, here are some of the possibilities that I can imagine:
  • Similar to their handling of absolute versus relative links, having the parser behind the scenes recognize relative links and perform similar "magic" to prevent a full re-render/re-auth would enhance the user experience for links intended to keep the user within the application.
    This could also be extended to trap event bubbling within click event of the generated link, which ties into the third feature request above
  • Similar to their handling of images and emojis, offering a specific syntax to support the insertion of one of the built-in icons by name (in addition to the special handling of relative links mentioned in the previous bullet) would make it possible to create your own "My Pages" widget - and so much more (e.g., if icons for folders happens, then the Catalog Quick Access markdown widget on the demo homepage could be updated to use matching icons for each button instead of the emojis current present).
  • Similar to what I would imagine is used behind the scenes for rendering action cards, offering a specific syntax to support the insertion of a button to trigger the opening of the modal-based form for triggering a self-service action