A small Node or Python script parses the README headings as categories and the markdown table rows as plugin entries. Each entry becomes an object with slug, name, repo, category and a short description. The script writes the array to data/neovim-plugins.json, which SleekRank then reads on render.

Yes. A nightly job calls the GitHub API for each repo in the JSON, merges the new stars and last commit date into the existing rows, and overwrites the file. SleekRank picks the values up because every plugin page renders from the file rather than from a frozen WordPress post.

Either remove the row or add a status field with a value like archived. The Twig template can render a deprecation notice when status is set and the sitemap can drop the URL. Because the JSON drives both, the listing page and the detail page agree on the plugin state.

No. SleekRank exposes a helper that filters the JSON by category and excludes the current slug, returning up to six related plugins ordered deterministically. The plugin page reads that list and renders cards, so related links update whenever the JSON file changes.

SleekRank parses the JSON on first hit and caches a slug-to-row map, so individual page render is an O(1) lookup. WordPress full-page cache then absorbs repeat traffic. The size of the JSON has almost no impact on per-page latency.

Yes. The /neovim-plugin/ index reads the array and renders a sortable list grouped by category. The /neovim-plugin/{slug}/ detail pages each pull a single row. Both reuse the same fields, which keeps title and description consistent between list and detail.

Use a canonical slug field and an optional alias array on each row. The template renders the canonical name as the title and lists known forks under an aliases section. SleekRank can also redirect alias slugs to the canonical /neovim-plugin/{slug}/ page through a small rewrite rule.

The page group accepts JSON out of the box. For TOML or YAML you can convert the file at build time with a small script that produces the JSON SleekRank expects. The render pipeline is the same once the array is in place.