Contribute

Have you been working with a technology that you think deserves a place on the radar? We welcome suggestions for new blips across all four quadrants:

• Techniques — Development practices, architectural patterns, or methodologies.
• Platforms — Infrastructure, cloud services, or runtime environments.
• Tools — Software that supports development, testing, deployment, or operations.
• Languages & Frameworks — Programming languages or the frameworks built around them.

When suggesting a technology, it helps to include:

1. The name of the technology and which quadrant it belongs to.
2. A brief description of what it does and why it's noteworthy.
3. Your experience with it — what worked well, what didn't, and in what context.
4. A suggested ring placement (Adopt, Trial, Assess, or Hold) with reasoning.

Open an issue in the repository to submit your suggestion.

Technologies evolve, and so should their placement on the radar. If you believe an existing item should move to a different ring — whether closer to the center or further out — let us know.

A reassessment request is most useful when it includes:

• The current blip and its ring placement.
• The ring you believe it should move to.
• What has changed — new releases, shifting community adoption, your team's experience, or emerging concerns.

Open an issue in the repository to request a reassessment.

Found something broken on the radar? Whether it's a rendering issue, incorrect data, a broken link, or a problem with the interactive visualization, we want to know about it.

A good bug report includes:

• What you expected to happen.
• What actually happened.
• Steps to reproduce the issue.
• Your browser and device (if it's a visual or interaction issue).

Report a bug in the repository.

If you've found a bug and know how to fix it, we welcome pull requests. The project is built with Astro, Vue, and TypeScript on the frontend, with a Go CLI for content validation and generation.

To get started:

1. Fork the repository and create a branch for your fix.
2. Make your changes, ensuring they follow the existing code style and patterns.
3. Test your changes locally by running bun run dev in the web/ directory.
4. Submit a pull request with a clear description of the bug and your fix.

Have an idea to improve the radar experience? We're open to enhancements that make the radar more useful, accessible, or easier to maintain. Some areas where contributions are especially welcome:

• Accessibility — Improving screen reader support, keyboard navigation, or color contrast.
• Visualization — Enhancements to the interactive radar chart or blip detail pages.
• Search and filtering — Better ways to find and explore technologies.
• Content tooling — Improvements to the CUE validation schemas or the Go CLI.

For larger changes, consider opening an issue first to discuss the approach before investing time in implementation.

All contributions — whether suggestions, bug reports, or code changes — follow the same general process:

1. Open an issue describing the suggestion, bug, or enhancement.
2. Discuss the approach with maintainers if the change is non-trivial.
3. Submit a pull request if you're contributing code or content changes.

We appreciate contributions of all sizes. Even small improvements like fixing a typo in a blip description or clarifying a ring placement help make the radar better for everyone.