The Themer’s Guide at https:\/\/theeventscalendar.com\/support\/documentation\/events-calendar-themers-guide\/ instructs us to put our custom styles in tribe-events\/tribe-events.css, but I’ve wanted to use some of my custom styles on both event pages and non-event pages (like tag.php). To allow non-event pages to use these styles, I’ve moved them to my child theme’s style.css page and so far I haven’t seen any problems with the event pages using styles defined in style.css. <\/p>\n
Now, I currently have styles defined in style.css and tribe-event.css and I got to wondering whether the tribe-event.css style is strictly necessary. I tried putting the Themer’s Guide’s code snippet to change the metabox of a single event into style.css and it worked, so I’m wondering why the guidance is to put styles in tribe-events\/tribe-events.css instead of style.css. I think in my case, it makes the most sense to keep all styles in one place. Are there downfalls to that, or is the recommendation of using the tribe-event.css file basically to promote separation of concerns?<\/p>\n
-> @Andy: That’s sort of what I was wondering. So far, evidence shows that the style.css file gets precedence, so is the file load order deterministic? Have you seen evidence that the event stylesheet sometimes gets loaded after style.css?<\/p>\n","protected":false},"template":"","class_list":["post-118558","topic","type-topic","status-closed","hentry"],"yoast_head":"\n