CSS clutter ? Avoid page-specific CSS pls!

  • Resolved tdechangy

    (@tdechangy)


    5 years, 3 months ago

    Hi, your work seem quite nice BUT do I see an elephant in the room ?

    After a couple trials it looks that you are generating CSS for each and every single page by adding its ID. This would mean lots of useless CSS reload on site browsing, only to have another ID into it.

    I tried the “Global Style Kit” setting under Elementor Style settings. While that would be the good place to setup this, it doesn’t generate a single global CSS code for theming while it should.

    This leads in fact to another potential issue where any page which is not using Elementor wouldn’t reflect the selected “global style kit”. And this can be very annoying.

    What is your actual approach about this, would you ever/soon solve this ?

    • This topic was modified 5 years, 3 months ago by tdechangy.
    • This topic was modified 5 years, 3 months ago by tdechangy.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Ram Ratan Maurya

    (@mauryaratan)

    Hi there,

    Thanks for writing in and I totally understand your concern. I’d be happy to explain it:

    How it works:

    The way Elementor’s API works is, when we add our panels in Elementor’s page settings, they automatically become a part of the page and generates CSS for each page, automatically. Even in case of Global Style Kit set.

    What are we doing about it?

    Performance is definitely on our radar and it’s definitely our <b>main focus</b> going ahead. We’re working through to change how to Style Kit panel settings are saved inside Elementor and then generate a stylesheet for each Style Kit separately and simply enqueue it on the pages as per user preference.

    While we don’t have any ETA on it yet, this is what we’ve planned to do going ahead. I hope it clears things a bit.

    Let me know if there is anything else I can help you with. Thanks.

    Thread Starter tdechangy

    (@tdechangy)

    All right, thanks for the explanation and I wait to see your later release to ensure better performance.

    For the moment I used your generated code to be used as theming CSS. This allows to disable the plugin unless there is a real need for custom styled posts. This needed much cleaning, so it would be nice to give the ability to export the some code for global theming, but :
    – without the post-specific class (obvious)
    – putting together all selectors that use the same attributes (one group per color, bg-color.. etc)

    + By the way I will probably more use the following plugin on all projects to manage global colors which are usable in each editor, and generates variables with custom names : Central color palette

    The biggest limitation that I find here is that while editing those colors to change an old site for example, the colors previously used through the post editor etc will NOT be updated accordingly. But this is essentially related to the way how WP works.

    Depending on the project scope (with a blog or any editable post by the user) this plugin could also be used for the development process only or maintained for further post editing using the custom colors.

    Thx for the job already done.

    • This reply was modified 5 years, 3 months ago by tdechangy.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘CSS clutter ? Avoid page-specific CSS pls!’ is closed to new replies.

Tags