Refactor: Migrate main site to Tailwind and archive Bootstrap content #87
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
…zation, integrate modern assets, and introduce Tailwind CSS.
adamswonder
previously approved these changes
Jan 3, 2026
JudahSan
dismissed
adamswonder’s stale review
The merge-base changed after approval.
adamswonder
approved these changes
Jan 4, 2026
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.
Summary
Prepare 2026 conference content: update layout, integrate modern assets, and introduce Tailwind CSS.
Key Changes
New UI: Main site refactored to use Tailwind CSS.
Legacy Support: Existing Bootstrap content moved to an archive directory.
Routing: Configured independent environments for both frameworks, connected via URL-based navigation to ensure no CSS conflicts.