@Szabolcs I have installed your latest IGraph/M release on Windows 10 (MMA 11.3) and tried a few random examples from documentation. Everything worked as expected.
@JohnFultz One thing I would really like to see if better support for cross-version-compatible packages. For example, what I expect from the documentation tools is to be able to produce decent looking and usable documentation that works and displays correctly in all target versions. I do not necessarily want beautiful documentation that looks just like the built-in one. Instead, I want some reassurance that if I produce docs with version X, they will work perfectly in version X+3 too.
You might have seen the monster notebook that is the documentation of IGraph/M. At 240 pages it is so huge that it tends to expose problems in the FE, so I assume W support might have forwarded it to you more than once. It really wants to be broken into smaller pieces.
The problem is that after my experience making the MaTeX documentation (which use the Workbench doc tools), I simply do not dare use the official documentation tools anymore. I am afraid that when the next M version comes out, something will break badly, and it will take a lot of work to fix it.
Making the MaTeX docs was plenty of work, and that package has less than 5 symbols. IGraph/M has 280 symbols.
So my suggestion is: do compromise on fancy looks and features, but get the basics right and make it as robust as possible.
@Szabolcs And some way to have a build process from some light-weight master template would be nice. I tried this for myself and it works nicely, speeds up doc building, etc. That'd allow the IGraph/M docs source to not change much but have the final deployed stuff be clean and easy to work with.
