I'm changing my comment to reflect new info. So the component isn't a unibody, it can still update changes sitewide without changing edited areas such as classes. GTK
Hi JSIKKEABSKS, I think you may have misunderstood how the components work or I don't quite understand your comment. Sorry I didn't explain a little better. Adding an editable action to a particular component just means that that the part of that component that is identified won't update with a global component update. Any other change will update all instances. So, if we wanted to change the name of the "Resources" menu item to "Examples", changing it in the original component will update it on all pages. The only thing that will not change is the presence or absence of the "active" class. So the global update will still be working.
A followup on building this navigation would be nice.
What would you like to see?
@@BoDonkey How to connect the dots. Meaning how to connect the navigation to the pages.
please release a video on installing the template on Woocommerce using Pinegrow Theme Converter or Web Editor
Very good tutorial!
Thanks a lot!
This is great!
I'm changing my comment to reflect new info. So the component isn't a unibody, it can still update changes sitewide without changing edited areas such as classes. GTK
Hi JSIKKEABSKS,
I think you may have misunderstood how the components work or I don't quite understand your comment. Sorry I didn't explain a little better. Adding an editable action to a particular component just means that that the part of that component that is identified won't update with a global component update. Any other change will update all instances. So, if we wanted to change the name of the "Resources" menu item to "Examples", changing it in the original component will update it on all pages. The only thing that will not change is the presence or absence of the "active" class. So the global update will still be working.