-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Custom Theme-ability... #29
Comments
Not sure if I can do it in the near future, but it makes sense. I also have clients using Sveltia CMS (as is). WIll put this on my to-do list! |
TBH cannot use it until Rich Text Editing is in place, because of the non technical people that would be using it, but excited for that day to come :-) |
Been messing around with CMS ideas myself in the last year or so: https://svelte.dev/repl/14075540b84440008848739b6fcb70a1?version=3.59.1 XD |
I think most things are controlled by css custom properties, so maybe being able to override the interval style sheet with another user generated one might be all that I need for now...dunno how easy that would be to include, of course :-) |
Yeah, some basic colours, fonts, etc. are written with CSS variables, so you can override them by adding a stylesheet to <!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="robots" content="noindex" />
<title>Sveltia CMS</title>
</head>
<body>
<script src="https://unpkg.com/@sveltia/cms/dist/sveltia-cms.js" type="module"></script>
<style>
body {
--font-family--default: Verdana;
/* and whatever */
}
</style>
</body>
</html> |
great, thank you XD |
Well, I need to say, Sveltia UI is still early/private beta with no documentation, and some (many) of these property names may probably change without notice in a couple of months. My plan is to ship the first public beta by August. CSS variables are very convenient anyway! |
no worries, you are doing amazing stuff so far and I am very grateful for this :-) |
hmmm...I was thinking...maybe just add custom theming classes to the elements in the cms...like...haven't thought this through too much, but simply adding some classes to elements and not styling to those classes. so that I could create a css file like and grab not sure how easy and/or feasible that is, though... and/or css custom properties for more of a configuration approach... |
One way to migrate to more variables is to skip adding them in a centralized place (for now) and just start using them where fit, with current values as fallback. E.g. |
I would absolutely love to be able to customize the look and feel of the CMS UI in the following ways:
I would basically love the ability to customize the general look and feel for clients and configure all that in a css file or something...
Please consider this in the near future, thank you ( ありがとう :-)
The text was updated successfully, but these errors were encountered: