feat: add new Tailwind-based style and visual improvements to site #442
Conversation
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
- Introduced Tailwind CSS via CDN for rapid prototyping and modern utility classes - Added custom theme colors (brand, primary, accent) to Tailwind config - Implemented new topbar, header, and background decorations for a fresh look - Enhanced theme card selection visuals and added a prominent GitHub "Contrib" ribbon - Improved responsive layout and accessibility for navigation and call-to-action buttons - Updated contributors section to dynamically load GitHub members - Refactored and modernized overall HTML structure and CSS for maintainability This update brings a modern, visually appealing, and more maintainable style to the Vim Bootstrap site, leveraging Tailwind CSS and improved UX patterns. Signed-off-by: Avelino <31996+avelino@users.noreply.github.com>
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.
fixed: #434
fixed: #417