Is it possible to edit plugin components?

Hey folks -

We utilise the discourse-solved plugin in our community, and we’d like to make it more clear from the topic index list pages (latest, category,new, etc… pages.)

When a topic is solved it has the checkbox visible in the title:

…But we’d like to either make that more bold, or coloured to highlight the solved topics.
Essentially we want to make it as simple as possible for our users to find answers.

Is it possible using the theme editor to alter the appearance of this component? as it’s a plugin component I am skeptical about that.

Alternatively, are there any other suggestions for achieving this goal?

Thanks in advance,
Ryan.

If it’s only css you can edit anything from your theme.

What have you tried so far?

5 Likes

@joffreyjaffeux

Currently very little - the appropriate CSS classnames/ids are unclear from here:

https://github.com/discourse/discourse-solved/blob/master/assets/stylesheets/solutions.scss

(or elsewhere in the discourse-solved repo form what I can see)

So while CSS changes in the theme are easy enough - I’m pretty new to discourse themes & plugins so I’m not sure the best/easiest way to find the appropriate attributes to target in my theme.

Easiest solution is to inspect generated html using your browser console. This way you will get exact classnames you want to change.

5 Likes

As said Joffrey, you can play with the browser inspection console.

Do you have already in mind what you would change?

If just the color, possible example:

If you don’t know how to apply CSS changes for your theme, this link should help you: Beginner's guide to using Discourse themes

8 Likes

Thanks all, got this figured out :smiley:

1 Like

Can I edit and test the javascript code (and not the css) of the plugin from the console (chrome/firefox) . Is this possible?
///
Generally how to test a plugin that edits on github? Do I have to upload a modified package every time, rebuild the forum (wait 8 minutes…) and test it on my own?

If you want to test away from your live site then you can set up a staging copy on another VPS, or a development environment on your computer. Either will allow you to test plugins out.

The development environment won’t require a rebuild every time, whereas the staging environment will let you carry out a representative test that closely represents your live server. Both have their own merits.

I don’t really understand what you mean by writing a staging copy.
Why i don’t have /.rebuild app on a local host?

after all, this is the procedure for installing the plugin ? or perhaps it is another way to install discourse plugin ?