256 library has groundworkcss instead of stylecss in latest builds - #268
Merged
willbreitkreutz merged 2 commits intoMay 11, 2026
Conversation
|
Please set a versioning label of either |
willbreitkreutz
approved these changes
May 11, 2026
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
2 participants
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.
Uses
groundwork.cssgoing forwardUpdated docs to reflect this
If a user has
style.cssnow and they bump to latest it should work without them having to usegroundwork.css.If we ever want to enforce style.css we may want to come up with a way to throw an error.
Some kind of deprecation css class in only
style.cssthat JS reads on load to say "style.css is no longer used >link to issue<".Patch bump since this should work both ways (style or groundwork css)