feat(assets): curate logo variations and add browsable gallery#92
Merged
feat(assets): curate logo variations and add browsable gallery#92
Conversation
- Introduced multiple SVG variations for logos, including designs focused on hammer and diamond themes. - Added HTML previews for different logo versions (v2, v3, v4). - Created documentation for logo generation prompts and a catalog for logo variations.
- Adjusted hammer and glow effects for better centering and positioning over the anvil. - Introduced new radial gradient for silver glow effect. - Enhanced spark placements for both steel and chrome variations to align with the anvil impact.
… element positioning - Added radial gradients for gold and silver glow effects to enhance visual appeal. - Updated element positions and sizes for better alignment and aesthetics across multiple logo variations.
…ects - Introduced multiple new HTML previews for logo variations (v5 to v11) showcasing different styles and animations. - Added numerous SVG variations with unique designs, including particle effects and plasma themes, to expand the logo catalog. - Included new assets for improved visual representation and user engagement.
- Created interactive HTML catalog displaying all 1,081 SVG assets - Organized SVGs into 9 categories for easy navigation - Added click-to-select functionality with visual feedback - Implemented search feature to filter SVGs by ID or filename - Added copy-to-clipboard for selected SVG IDs - Each SVG has a unique human-readable ID for tracking
- Added all 1,081 SVG files as backup - Created svgs-to-keep.txt listing the ~35 SVGs to retain - This commit serves as a restoration point before removing unwanted SVGs
- Removed 1,042 SVG files to streamline the assets folder - Kept only the best variations across categories: - Lightning effects (5 variations for dynamic energy) - Chrome styles (3 minimal, precision, and strike variants) - Particle animations (7 experiments with optimized effects) - Motion designs (8 flow and animation variants) - Forge/hammer concepts (4 metalwork-inspired designs) - Essential SVGL icons (6 framework/tool logos) - Updated SVG catalog to reflect simplified collection - Reduced total SVG count from 1,081 to 39 files - All removed files backed up in previous commit for recovery if needed
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
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.
The logo design process generated hundreds of SVG variations across 12+ iteration rounds. A previous commit curated these down, but the 17 HTML preview pages were never updated — leaving every single one broken with dead
<img>and<object>references to deleted SVGs.This branch consolidates the logo assets into a clean, browsable state: 33 curated SVGs organized by design category, a single
gallery.htmlthat actually works, and removal of all the broken preview pages.The gallery page has light/dark/gradient background toggles and S/M/L size controls per logo, so you can evaluate each variation in context. No source code, tests, or library functionality is touched — this is purely
assets/logo/housekeeping.