Refactor diagram handling, enhance formats, and add SVG templates#28
Merged
Conversation
- Updated artifact-queue.md to clarify storage locations for high-level diagram references, SVG images, optional Mermaid Markdown, and HTML artifacts. - Revised diagram.md to specify the use of SVG as the default output and to include HTML as an optional format. - Enhanced overview.md to reflect changes in diagram storage and output formats. - Modified README.md files in diagrams, images, and html directories to provide clearer guidance on usage and generation rules. - Introduced a new diagram.html template for generating standalone HTML diagrams with inline SVG support. - Updated cli.py to classify HTML files as project-owned artifacts. - Added tests to ensure proper handling of new HTML diagram artifacts and validate the standalone nature of generated HTML.
…agrams - Created a new SVG file for a sequence diagram with customizable elements. - Added a state lifecycle diagram SVG template with defined states and transitions. - Introduced a timeline plan diagram SVG template featuring phases and milestones.
…tecture input and updating SVG template selection rules
…to visual contract - Updated font-family in SVG and HTML templates to remove proprietary font fallbacks, ensuring compliance with the Apache-2.0 distribution guidelines. - Ensured all generated SVG and HTML visual outputs follow the shared devspec dark visual contract, including background colors, text colors, and typography. - Maintained consistency across various diagram templates including architecture, domain model, journey map, mindmap, process flow, sequence, state lifecycle, and timeline plan diagrams.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request updates the devspec diagram and extract workflow to make SVG the default diagram output format (instead of Mermaid), and expands support for output format combinations to include
svg,html, andmermaidin any non-duplicated combination. It also updates documentation, agent, and skill files to reflect these changes, clarifies how diagram input is parsed, and adds new intake patterns for architecture and other diagram families.Diagram Output Format and Workflow Updates
/devspec.diagramand related commands from Mermaid to SVG, and updated all references and documentation to reflect this.Diagram Input and Intake Pattern Enhancements
Template and Artifact Handling
Other Improvements
These changes make the diagram generation workflow more flexible and consistent, improve clarity for users, and ensure better alignment with the intended visual standards.