Schedule a daily sync that hits the Hex.pm packages API with a since-timestamp parameter and updates only changed rows. SleekRank regenerates just the affected pages. The full corpus stays incremental, so sync runtime stays bounded. The dateModified field on each row drives the JSON-LD payload so search engines pick up freshness signals automatically without manual editor intervention.

Yes. Hex.pm exposes a retired field per release with a reason and message. Map both into a retirement JSON object per row. The page renders a clear retirement banner with the suggested successor linked when the message points at one. The sitemap keeps the URL alive so external code still resolves, and search engines reindex with the retirement context surfaced in the title.

Add a language enum column (elixir, erlang, both). A badge on each page surfaces the primary language, and /elixir/hex/language/erlang/ index pages list every pure-Erlang package. Readers writing Erlang projects filter directly to packages compatible with their toolchain without scanning mix.exs metadata or rebar.config conventions for each candidate library individually.

Each row carries a related_packages JSON array curated from the description text and the category overlap. A list mapping renders a related-packages block on every page. The clusters update on each sync as new packages enter the registry. Editorial overlays can add hand-picked recommendations on top of the automatic clusters when a particular package needs human judgment.

Yes. Every release on Hex.pm publishes generated documentation at hexdocs.pm/{name}/{version}. Store the docs URL per release in the releases JSON array. The page renders a docs link strip on every release in the timeline, so readers jump directly to the right API documentation without having to construct the URL manually for each version they care about.

Each page carries a unique description, unique version history, unique requirements table, unique Elixir and OTP compatibility data, and unique download metrics. That is genuinely unique structured data per page. Search behavior matches npm and crates.io, which rank reliably across hundreds of thousands of packages because every entry is genuinely distinct and updated as releases ship.

Yes. Each package carries category strings derived from the description and from any extra Hex.pm tags. SleekRank generates /elixir/hex/category/{category}/ index pages ranked by recent downloads, latest release, or compatibility. Keyword-based clusters can be added by parsing description text or by maintaining a curated keyword overlay file alongside the registry-sourced dataset for editorial control.

Append the new Elixir version to elixir_versions on every package that builds against it as community build reports come in. The compatibility badges and the /elixir/hex/elixir/{version}/ index page update on the next sync. Editor cost per new Elixir release is one configuration field. Packages that fail against the new release carry a clear incompatibility note driven by automated build data.