Simplified MultiDocumenter.jl

[icweaver]

PR doc preview: https://JuliaAstro.github.io/previews/PR44/docs/

Currently, we need to keep 4 different places in sync manually when referring to packages:

• docs/pages.jl - inlined with docs/make.jl in this PR
• docs/src/ecosystem.md - auto-generated in this PR
• docs/src/highlevels/<package category>.md - removed completely in this PR in favor of the ecosystem page
• test/runtests.jl - list of packages to test now auto-generated in this PR

I feel like this can make doc maintenance pretty error prone. To help alleviate this, this PR instead treats src/JuliaAstroDocs.jl as our single source of truth.

Tracking navbar item overlap issue here for smaller screen sizes: JuliaComputing/MultiDocumenter.jl#35

• Using more succinct navbar item names to get around this, which may actually be preferable if this looks alright to y'all

Other changes

• New packages added and links cleaned up
• astropy comparison page. Promoted by this discussion: https://discourse.julialang.org/t/mapping-julia-s-astronomy-package-ecosystem-bridging-gaps-and-highlighting-strengths/128249

[icweaver]

Apologies for the last minute additions. This discussion inspired me to add in an astropy comparison page. Happy to move it to a separate PR though if preferred

[abhro]

The way the comparison tables are written, especially for multiple packages in a single row, makes the description seem clunky. We could do one row per package and have the python counterpart span multiple rows, but I don't think that's feasible in basic markdown without also writing HTML :(

[abhro]

Does the deploy need to be under a conditional? IIRC, deplyodocs automatically identifies if it's in a CI and so if it needs to run.

[icweaver]

Yea, it still throws a warning though, so I just did this to get around it. No strong feelings either way tho

[icweaver]

xref: #47 (comment)

[icweaver]

The way the comparison tables are written, especially for multiple packages in a single row, makes the description seem clunky. We could do one row per package and have the python counterpart span multiple rows, but I don't think that's feasible in basic markdown without also writing HTML :(

Oh I absolutely agree. The dream would be do have something like CommonMark.jl support MichaelHatherly/CommonMark.jl#41, then we could sprinkle in some <br>s to get some breathing room. As you saw, my poor workaround was to just split items with | character for now just to get something standing

Update: work around here: #61

[icweaver]

I noticed that we have a good amount of real estate in the dropdown menu, so I also included the associated brief taglines for each package to try and make things more descriptive for newcomers (52d86c2). Was pretty easy to add with the new autogen system we're trying, and seems to work well on mobile and with line wrapping

idk, still playing around with it. What do you think?

[abhro]

I noticed that we have a good amount of real estate in the dropdown menu, so I also included the associated brief taglines for each package to try and make things more descriptive for newcomers (52d86c2). Was pretty easy to add with the new autogen system we're trying, and seems to work well on mobile and with line wrapping

idk, still playing around with it. What do you think?

Hmm, that might end up being too cluttered.

[icweaver]

sg, just put back (d4ef2fd)

[abhro]

Everything looks good! Merging