The fix will most likely entail replacing @plone-font-weight-light with @plone-font-weight-regular in a less file.
I've made the change but I expected grunt watch to just detect it and then be able to see the change in my live site. Is there a step I'm missing?
I really want to see that the change has been effected before doing a pull request.
If I understand things correctly, Plone 5 will compile LESS without grunt, so I'm not sure if the whole grunt watch thing was even needed to fix this bug. Can anyone clarify this for me?
Barceloneta diazo css/less is not registered on the registry of plone in order to enable zip themes to be loaded.
So, if you work on less from barceloneta on plonetheme.barceloneta you need to compile it with the gruntfile that is on the package. In diazo themes we defined the less/requirejs development files and css/js production files on the manifest.cfg so when you are on development on plone you also get the source of the code. As its not defined as a bundle you will not be able to compile it on Plone (we had a discussion on Bristol to enable that barceloneta can be a theme without profile).
Conclusion:
If you want to modify plonetheme.barceloneta less you need to run grunt less or grunt watch on plonetheme.barceloneta src folder.
Notes
-----
- You may want to enable Development Mode in the Site Setup -> Resource Registries to see your changes.
- If you want to modify plonetheme.barceloneta LESS you need to run `grunt less` or `grunt watch` on the plonetheme.barceloneta src folder