Skip to content

Improve visibility and structure of the “MDAKits and MDA-based tools” page #489

@PicoCentauri

Description

@PicoCentauri

Summary

The current presentation of the “MDAKits and MDA-based tools” page may unintentionally discourage developers from registering their software as an MDAKit and could give a misleading impression about the state of the MDAnalysis ecosystem.

Image

Background

MDAnalysis distinguishes between:

  • MDAKits: packages that meet certain standards and are regularly tested against MDAnalysis (following the MDAKit guidelines and registry process).
  • MDA-based tools: software that simply uses MDAnalysis, without being officially registered as an MDAKit.

The page currently lists these in two sections:

  1. A short paragraph describing and linking to the MDAKit registry, without showing any kits directly.
  2. A long, explicit list of “non-MDAKit registered” tools using MDAnalysis.

This structure means that readers who scroll down quickly are immediately presented with the “non-MDAKit” tools, which:

  • May draw attention away from MDAKits (which are the recommended standard).
  • Undermines the motivation to turn one’s project into an MDAKit.
  • Likely underrepresents the broader MDAnalysis ecosystem, since many tools using MDA are not listed there.

Problem

Because the MDAKit registry is only linked (and not shown), while the list of non-MDAKit tools is explicitly visible:

  • Visitors are visually and psychologically drawn to the longer, detailed list.
  • The distinction between “endorsed/standardized” and “just using MDA” tools is blurred.
  • MDAKits do not get the visibility they deserve, despite being the projects that adhere to the ecosystem’s best practices.

Suggested Improvements

A few possible directions I could think of

  1. Display MDAKits directly on the page. Maybe there is good way of not having them as by hand duplicate from the mdakit website.
  2. Make the MDAKit section visually dominant (e.g. longer, with visuals, banners or icons) and the “non-MDAKit” list follows as a secondary section.
  3. Consider splitting the pages, e.g.:
    • /mdakits/ (showcasing all registered kits)
    • /tools-using-mda/ (optional curated list of other tools)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions