Making Guru more transparent in terms of CSS

rogermont

Hello,

I believe it would be a good idea to have an option to make Guru more transparent in terms of the styles introduced by its CSS stylesheets.

Every site has a different look and style, and ideally every component should be as transparent as possible in terms of the CSS it uses.

Guru uses many CSS files, and some of these can change drastically the way the website looks. We are finding that every time we update Guru, we need to do a thorough check of the update and "fight" the new styles that don't look at all as our website. This is very time consuming and not practical.

It would be great if Guru had an option in the backend to "Only load essential CSS". When activating this option, only one CSS file would be loaded by Guru, with the essential styles needed to function (opening modals, etc.). The rest would be left to the style of the site.

This way, Guru would be able to integrate seamlessly into almost every website out there, making it much more versatile for many more types of users.

Could you please consider adding this option to the next release?

Thank you.

Best,
Roger.

saguaros

Hi Roger,

The current structure of CSS files are defined from former Guru team. I will forward your suggestion to our Guru team for further consideration.

Thanks for your input!

rogermont

Thank you Saguaros!

rogermont

Hi Saguaros,

Did you hear back from the Guru team about this topic?

Thank you.

Best,
Roger.

saguaros

Hello Roger,

I completely empathize with your situation. Yootheme and Guru have extensively relied on Uikit classes as a core styling component for quite some time now. Removing these classes from the Guru component would entail a substantial and time-consuming task. Unfortunately, our current resources are limited, making it unfeasible at this point in time.

Your understanding in this matter is greatly appreciated.

Thank you.

rogermont

Hi Saguaros,

Thank you for your message. I understand you need to prioritize the resources available, and I thank you for doing it as that makes Guru a better component for all of us.

What I propose in this thread is not replacing all the classes, but splitting the existing CSS styles into two different files:

One would contain the absolute indispensdable CSS code needed for Guru to function (let's call it guru_core.css) and another file (let's call it guru_extended.css) would contain all the other CSS styles. A new option in the backend "Load Only Core CSS" could be activated on demand by the user, so only the core CSS style would be loaded when active.

This option would be inactive by default, so the change would not cause any disruption to the users that don't need it. And it would be a total life changer for those users that need it, as ti would save us a lot of time.

In my opinion the styles needed in the CORE file are really small. I'm happy to create an example of it for you guys to evaluate.

Thank you for taking this idea into consideration.

Best,
Roger.

saguaros

rogermont Yes, I do get your point but it would be the same effort so it's not available for now, unfortunately 🙂

rogermont

Hi Saguaros!

Thank you for your reply.

I understand it might sound like a complicated task, but the effort to implement that change is no more than 5 minutes, 10 minutes tops.

Once the two CSS files have been created, there's only need to create a new option for the backend, and to add an if statement. It is pretty straightforward.

The most time consuming task is splitting the CSS file, and we'd be happy to provide that to you.

Thank you for your kind uderstanding.

Best,
Roger.

saguaros

rogermont Thanks for your input but as I mentioned, we have limited human resources for now, who are working fulltime for the new monthly templates and migration task 🙂