@josh Yeah, my thoughts are that this seems to be a relatively difficult and even then testy thing to solve with automation. As you mentioned D8 gets way more granular re: whats loaded in a given page at a given time. If we shift our thinking re: this problem from a “feature” to a “workflow” or “best practices” approach, We can imagine that setting up a baseline set of includes to give us a “good baseline set of drupaly css and js includes”… is just another one of those tasks that we recognize and set aside time for like: “set up living style guide” … we could have “establish sites baseline asset includes in port and style guide”… then in the time it takes to see which things we want to include and populate an array/config in both style guide and prototype and were done. Not exactly the most elegant solution, but if we’ve found anything it’s that solving this one has been consistently inelegant. This way it’s at least “part of the plan and not hard” Thoughts?

…

On Dec 13, 2016, at 6:57 PM, Josh ***@***.***> wrote: @thiagodemellobueno <https://github.com/thiagodemellobueno> you had thoughts today on an approach and/or whether this was still a thing that module needed to do. Care to elaborate? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAE1dVhQNy1WGLxOHu7VQH76nGcymXU7ks5rHzDPgaJpZM4LA6LA>.

Drupal assets #22

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions