• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space

Move /lib/Peafowl/peafowl.css to /app/themes/

A

ashkir

đź‘˝ Chevereto Freak
đź’ˇDescribe your idea

When I was redesigning the CSS for my site, I wanted to use the dark version or "Blacky" version of the CSS as a jumping off point as I recolored things one by one. It confused the hell out of me at first when I was using the regular /app/themes/style.css on light and dark, to find nothing was changing! Everything was being ignored. Then I realized everything you make to the style.css is overrideen by /lib/Peafowl/peafowl.css.

Can we get peafowl.css moved over to the theme folder or merged with style.css eventually? This was a very weird experience to have to go outside the theme folder just to update a theme.
 
ashkir said:
I realized everything you make to the style.css is overrideen by /lib/Peafowl/peafowl.css.
Click to expand...
In CSS you can override anything, anywhere. It just requires to use the same selector (if the file is called after) or simply use a stronger selector. If everything fails, you can always use !important to make your rule top priority.

I haven't updated myself on modern CSS markup/delivery, but certainly we will use theme level dependencies, not "framework" level to avoid the issue you are mentioning here.
 
You must log in or register to reply here.
Back
Top