-
Notifications
You must be signed in to change notification settings - Fork 140
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
feat: visually editable site theme #1614
feat: visually editable site theme #1614
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
<NextIntlClientProvider locale={locale} messages={messages}> | ||
<NuqsAdapter> | ||
<MakeswiftProvider previewMode={draftMode().isEnabled}> | ||
<MakeswiftProvider previewMode={draftMode().isEnabled}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved up <MakeswiftProvider>
so that it wraps the whole document, including <head>
where <CssTheme>
is injecting the styles.
--contrast-200: 0 0% 82%; | ||
--contrast-300: 0 0% 70%; | ||
--contrast-400: 0 0% 54%; | ||
--contrast-500: 0 0% 34%; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved out of CSS to a Typescript file so we can reuse these values in theme component registration to provide props with default values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if there's a better way than deleting things for when we need to separate Makeswift related integration code from main. Ideally we don't have to delete anything from the base repo, just add Makeswift related code. Maybe that's wishful thinking.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good goal and we can accomplish it by overriding these values with Makeswift CSS variables further down. That being said, sometimes conflicts are good as we would want to know when this list changes to that we can do the equivalent change on integrations/makeswift
.
8223d94
to
e73a2e5
Compare
e73a2e5
to
698c6cb
Compare
--contrast-200: 0 0% 82%; | ||
--contrast-300: 0 0% 70%; | ||
--contrast-400: 0 0% 54%; | ||
--contrast-500: 0 0% 34%; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm wondering if there's a better way than deleting things for when we need to separate Makeswift related integration code from main. Ideally we don't have to delete anything from the base repo, just add Makeswift related code. Maybe that's wishful thinking.
Kapture.2024-11-10.at.23.24.02.mp4