How zalando/tech-radar works
• Static Web Client: The user’s browser that loads and renders the Tech Radar.
• Visualization Library (radar.js): The core script (located under docs/radar.js and the versioned files in docs/release) responsible for generating the radar visualization.
• External Dependencies: d3.js (a dependency loaded via CDN) that powers the rendering and manipulation of SVG elements.
• Configuration and Assets:
• The docs folder contains additional assets (index.html for the demo, config.json, radar.css, and multiple release versions of radar) that define the visualization’s style and behavior.
• The package.json and other configuration files (.eslintrc.json, .npmrc, etc.) that serve for development and code quality.
• Development Environment: A local dev server (launched via “yarn start”) which is used when running the project locally.
• Deployment Context: As a static page, it can be hosted on any static page hosting provider, as emphasized in the README.
Relationships and Interactions
• The browser loads an HTML page (e.g., docs/index.html) that includes:
• A link to the external d3.js library (via CDN).
• A script tag that points to the radar visualization script (radar.js from either the docs folder or one of the release versions).
• An SVG container (with a specific id) that serves as the rendering canvas.
• During development, files are linted and the project is managed using standard tools (Yarn, ESLint, etc.), indicating a strong emphasis on code quality.
• The relationship between static assets (HTML, CSS, JavaScript) is straightforward – each layer contributes to assembling the final visualization.
Architectural Patterns and Relevant Technologies
• Static Client-Side Rendering: The entire visualization is rendered within the client’s browser using SVG and d3.js.
• Modularity via Versioned Releases: Multiple versions of radar (e.g., radar-0.11.js, radar-0.10.js, etc.) allow users to select a specific version as needed.
• Configuration-Driven Design: The visualization is highly configurable using a JavaScript object that defines visual parameters and data layout.
• Development Best Practices: The presence of code quality files (.eslintrc.json, .gitignore, etc.) shows adherence to linting and modular coding practices.