Point SleekRank at the TAP REST endpoint of the NASA Exoplanet Archive or maintain a CSV mirror that you refresh on a schedule. Each cache cycle re-reads the source, so newly confirmed planets appear as fresh URLs and withdrawn planets disappear, all without editor intervention.

Yes. The Twig template receives every field on the row, so you can render orbit diagrams, transit light curves, or size comparisons keyed off the planet's own mass, radius, and orbital period. The visualization code is shared, the data is per-row.

The slug column stays whatever you decided. If you want the URL to follow the rename, change the slug in the source and add a redirect from the old slug. If you want stable URLs, keep the slug and update only the display name field. SleekRank does not force a URL change.

Yes. Add a filter field on each row, like habitable_zone: true, and create a second SleekRank page group with a different URL pattern that reads only the filtered rows. Both groups can share the same source file and template.

Yes. SleekRank's related entries helper groups by any field you choose. Setting it to host_star automatically lists the other planets orbiting the same star, sorted by orbital period or another field of your choice.

SleekRank caches resolved rows in a custom table, so the 5,500-row archive is well within range. Sites running 30,000+ rows on the same plugin report normal page load times because each request only reads its own row, not the full catalog.

Yes. The template renders structured data using the row fields. Most sites emit CreativeWork or Dataset schema, with the planet name, discovery year, and reference DOI populated. SleekRank does not lock you into a specific schema type.

Yes. Add an extra field on the row, like editorial_html, and conditionally render it in the template. Planets without editorial content fall back to the data-only layout. The editorial content lives in the same dataset, so it stays attached to the planet it describes.