Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Rethink of tailwind backend #39

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

[WIP] Rethink of tailwind backend #39

wants to merge 2 commits into from

Conversation

jaxwilko
Copy link
Member

@jaxwilko jaxwilko commented Dec 1, 2023

I've been meaning to re-work this for a while.

So far I've stripped out the headless ui stuff, stuck in a Backend vue component, then pass the Winter rendered page in and render it inside the Backend component. I've wrapped the storm.css & winter.css files in .winter-portal so 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.

image

@LukeTowers
Copy link
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants