[WIP] Rethink of tailwind backend #39
Draft
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
Member
|
@bennothommo can we have your magic to mock up a pretty revamp of this skin that @jaxwilko can implement? |
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.
I've been meaning to re-work this for a while.
So far I've stripped out the headless ui stuff, stuck in a
Backendvue component, then pass the Winter rendered page in and render it inside theBackendcomponent. I've wrapped thestorm.css&winter.cssfiles in.winter-portalso the css is isolated to only the Winter rendered page.The menu is now a Vue component as a child of the backend and data is being passed in via root props.
A lot of stuff is broken currently.
My main goal is to add functionality for creating tailwind patch files for plugins to generate against the tailwind ui plugin's tailwind file, so that plugins can effeciently render their own tailwind css.