There are many aspects of QuotesDLX theming, so it's best to take a look at the sample SCSS file to get an idea of all the variations.
Sample Theme: a working sample theme is available to use as an example.
The Main CSS Wrapper
When your theme is created, QuotesDLX automatically adds a class to the base container that you can use for styling.
For example, if your theme slug is light-branded, then the CSS class you'll want to target is: quotes-dlx-block-theme-light-branded.
The prefix `quotes-dlx-block-theme-{slug} is a required format.
SASS File: you can check out .
Styling Tips
Use CSS Variables With Defaults
Your stylesheet should contain CSS variables in order to have a dynamic font size, font family, and a color palette.
Colors
For example, say that you've created a color with the slug bright-pink. When outputting the color in CSS, you should use a CSS variable to make it dynamic.
In this case, you can reference the color by using:
color: var( --qdlx-bubble-gum-accent, $accent );
The above $accent is a default declared further up in the stylesheet (if you using SASS).
Font families can be declared globally, or for the individual theme. The priority is the per-theme options over the advanced option. This is reflected in the following:
In the above example, you'll want to set your own breakpoints.
Setting Breakpoints
/* Responsive styles - In hindsight, should've used mobile-first */
/* Mixin from: https://css-tricks.com/snippets/sass/mixin-manage-breakpoints/ */
/* It's only used here, so no external file for mixin? */
$breakpoints: (
'xs': 420px,
'small': 520px,
'medium': 768px,
'large': 1024px,
'xl': 1200px,
'xxl': 81.1400px
) !default;
@mixin respond-to($breakpoint) {
// If the key exists in the map
@if map-has-key($breakpoints, $breakpoint) {
// Prints a media query based on the value
@media (min-width: map-get($breakpoints, $breakpoint)) {
@content;
}
}
// If the key doesn't exist in the map
@else {
@warn "Unfortunately, no value could be retrieved from `#{$breakpoint}`. "
+ "Available breakpoints are: #{map-keys($breakpoints)}.";
}
}
An attempt was made to have dynamic breakpoints, but unfortunately the CSS spec doesn't support this.
The Meatball menu typically resides on the top right of the interface. You'll have to plan for styling this menu, as well as its pop-up.
Testing Styles
Set a Default Theme
Set your new theme as the default. You can then right+click the theme and open a preview in a new tab. Here, you can modify the theme and have a preview of your changes.
View the Theme in the Theme Options Admin Tab
Navigate to Theme Options and you'll see your default theme selected here. If it's not reflected, you can switch to the theme using the theme dropdown.
You'll see a live preview if any colors are modified.
Additionally, you can set font variations and even custom font families. Each of these can easily be previewed.
Stylesheet Conclusion
In summary, to create your own stylesheet, you should:
Plan for variations
Use CSS variables for dynamic properties
Use sane breakpoints
Preview the theme changes in the Theme Options tab
The plugin's breakpoints are as follows as defined by a mixin included with .
