Good discussion taking place here.
@matjaz ,
I still believe this portion of the workflow should have some failsafes, as fragmented inline styles can occur for new users or even seasoned users inadvertently. If you recall I had mentioned it previously.
As it stands right now I believe this type of fragmented CSS can still presently occur and still remains to be considered even with the workflow as it currently stands at this moment.
You can go into Pinegrow and start using the new Visual CSS Editor, which by default creates a “inline style attribute” for the selected item you are working on. You can do this on as many items you like and Pinegrow will amass a list of “Classes without rules” which translates to all these visual edits placing inline styles on items.
The user can then save the file without warning and these inline styles will remain in place. Of course we know inline styles are largely frowned upon in general within the industry as it fragments the CSS workflow across locations and makes maintenance a nightmare to search for all the corresponding CSS instances in multiple locations. But having said that you can use it effectively, to create HTML emails which may require inline CSS, etc.
So what to do, or what can be done to help prevent this inline CSS fragmentation?
A developer should quickly learn or already be aware and know the current new Pinegrow CSS workflow already. But in the midst of working and using the Visual CSS Editor, or via on page direct item controls (as discussed in the first post), even a seasoned developer might let something inadvertently slip though as inline CSS. So it’s not just towards the newer less experienced user that this can occur or be a problem.
For Pinegrow 5 the main focus is improving the styling with CSS/SASS. What we have now is a powerful foundation, but some parts of the workflow are still awkward , for example, working with nested SASS structure.
Hopefully something regarding failsafes will be included in Pinegrow 5, so the occurrence or possibility for fragmentation is prevented throughout the styling workflow(s) for all users.
1 Like
