This repository was archived by the owner on Jul 31, 2025. It is now read-only.
Draft
Conversation
…erator - Add AOE Technology Radar as dependency - Configure quadrants (Languages/Frameworks, Platforms, Tools, Techniques) - Configure rings (Adopt, Trial, Assess, Hold) - Convert CSV data to markdown format with proper metadata - Add about page with Tech Radar documentation - Set up build scripts for static site generation
- Remove all references to CSV files and CSV-based workflow - Update build system description to AOE Technology Radar - Add detailed build and testing instructions - Add comprehensive contribution guidelines for markdown-based system - Update FAQ section with relevant questions for new structure
The CSV file is no longer needed after migration to AOE Technology Radar markdown-based system
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Should we consider changing the provider of the visualization to the AoE tech radar.
Claude and I converted the current repository over (one shot!), and this is what the branch looks like:
The big advantage I see is that we can now provide a Markdown file per technology.
This has the potential to be useful, because we could add more details that help support adoption of technology across Redgate. For example, the GitHub Actions page could give a summary of what we learned in "Trial" phase before moving to Adopt. Equally, being able to keep history "feels" nicer because we'd have a record of why around Kubernetes.
I do realize that the problem with the Tech Radar isn't technology, it's actually making this part of our processes. To date we've failed to do that, but I'm wondering if one of the reasons why was that the tech radar didn't capture the right information?