As see from #53 we can have broken/dead links, links that once worked can be unavailable for reasons outside the control of this project/repo!

Hence I have decided to manually scan (for now) the repo from time to time for such links and fix them - if there is one. Here are the steps to take:

New broken/dead links

• find missing links using, markdown-link-check (see https://www.npmjs.c

Building documentation for a paclet is tedious at best and I've never been able to successfully do it with anything other than Wolfram Workbench. It would be great if we could have similar functionality in this plugin because Eclipse really sucks compared to Intellij.

I have no idea if this is possible or how to go about it but I figured at least a discussion would be worth it.

Once #15 is implemented and we have a ::usage message for the integration-step condition function, this information should be included in the Steps display. I imagine for instance a tooltip when the user hovers over the green functions like IGtQ or GtQ

The implementation of this issue will require changed in [ShowStepFormatt

Domination is one of the most central concepts in (algorithmic) graph theory, but there's not a lot of support for domination in IGraphM. As a start, to extend the family consisting of IGDominatorTree and IGImmediateDominators, I'd suggest adding utility functions to verify whether a given subset of vertices form a dominating set.

To check if

There should be a documentation section that explains LibraryLink compatibility between Mathematica versions and also explains why different binaries are needed for 10.0-10.3 and 10.4 on OS X.

A small suggestion for DocGen family.

Since the target group are third party packages maybe generated symbols etc. notebooks should have CellContext -> Notebook or even Global` , though Notebook will be better.

The reason is Needs["myPackage`"] in an intialization cell does not do much since every cell group has separate $ContextPath. One still needs to use full names or change `