rollup/awesome

Purpose

This is a curated “Awesome” directory of Rollup ecosystem resources, plugins, and packages—not a Rollup plugin, application, or buildable software project. Its primary artifact is the repository documentation.

Primary Entry Point and Data Source

• README.md is both the public entry point and canonical dataset. It defines the taxonomy and stores each listing as Markdown link plus a short description.

• media/logo.ai is a source design asset; the README references media/logo.svg, but that SVG is not present in the supplied tree.

Content Taxonomy

The README organizes entries into architecture-level discovery categories:

• Resources and official Rollup guidance.

• Plugins grouped by responsibility: core, development/general-purpose, code quality, CSS, frameworks, module resolution, file imports, output, templating, text replacement, transpilation, and workflow.

• Packages split into Rollup-maintained and community offerings.

This taxonomy is the repository’s key information architecture and navigation mechanism: README.md.

Content Flow and External Boundaries

Contributors edit Markdown listings in README.md; rendered repository documentation presents those entries to users. Each entry points outward to third-party GitHub repositories, GitLab projects, npm, documentation sites, or service websites. The repository does not vendor, execute, validate, or integrate those external plugins/packages.

Primary boundary: local curated metadata in README.md versus externally hosted projects and URLs.

Contribution Governance

Contribution expectations and pull-request conventions are defined under:

• .github/CONTRIBUTING.md

• .github/PULL_REQUEST_TEMPLATE.md

These files govern how catalog changes are proposed and reviewed, rather than implementing runtime behavior.

Runtime and Infrastructure

There is no application runtime, package manifest, CI workflow, build configuration, source-code directory, or test suite in the supplied tree. GitHub is the material hosting/review infrastructure; Markdown rendering is the delivery mechanism. Repository metadata is limited to documentation, contribution templates, license, ignore rules, and media assets.