After upgrading to Discourse 2.7.0.beta1, HeyRR noticed they could no longer modify downloaded theme components like the Xmas hats component, though local-created components remained editable. michaeld clarified this is an intentional feature designed to prevent users from losing customizations when remote themes are updated — referencing a meta discussion. HeyRR acknowledged the oversight in their search and expressed that users should bear responsibility for maintaining their themes, valuing the convenience of in-place edits. michaeld countered that allowing direct edits risks breaking themes during updates, and recommends stacking modifications in separate components instead — referencing another meta topic — likening unrestricted edits to leaving out sharp knives, since warnings alone aren’t always sufficient to prevent issues.
Until something changes that impacts your theme component and you cannot update it because it would mean you would lose your modifications. Theme components can be stacked so you can (and should) put modifications in a separate component.
Sometimes it’s better to put away the sharp knives, since warnings don’t always work.