The popup that is used to format and render Markdown documentation files works relatively well and supports images and links to other pages (opened in tab). What it does not handle is navigation within the page because # links interfere with Angular # URL. One solution would be to implement a more advanced documentation visualization popup that has a table of contents that is auto-created from Markdown. This is similar to the page table of contents that Markdown shows. See also this example, which is too busy. It would be nice to have a Markdown viewer with table of contents as an option.
The popup that is used to format and render Markdown documentation files works relatively well and supports images and links to other pages (opened in tab). What it does not handle is navigation within the page because
#links interfere with Angular#URL. One solution would be to implement a more advanced documentation visualization popup that has a table of contents that is auto-created from Markdown. This is similar to the page table of contents that Markdown shows. See also this example, which is too busy. It would be nice to have a Markdown viewer with table of contents as an option.