You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In its current state, Canvas leaves much to be desired in the way of compiling assets and maintaining clean LESS code.
If you look at backend-css.blade.php and backend-js.blade.php, you'll see that all the files are kept in the assets directory and copied over to the public via gulp. The reason behind NOT using CDN's here was because I wanted to keep the integrity of the app/design/style for years to come. Using the specific stylesheets/scripts and not referencing a CDN meant that I could be 100% sure that the app itself would contain all it needed to survive. That does however take up disk space and ultimately weighs down the app with files that COULD be kept off-site. And for an app that prides itself on minimalism, this is something I've put thought into.
Curious to know anyones' thoughts on this and if someone who is very design-oriented/capable wants to take a stab at re-organizing the resource assets, I'd be excited to see what you could come up with.
Biggest stipulation here: The app needs to look/feel as it does in it's current state. Anything from animations to the styling needs to be consistent and be full-proof for future downloads. I know it's a big task, but you guys have already proven to be quite capable when it comes to helping out with this, so have at it. :)
The text was updated successfully, but these errors were encountered:
In its current state, Canvas leaves much to be desired in the way of compiling assets and maintaining clean LESS code.
If you look at
backend-css.blade.php
andbackend-js.blade.php
, you'll see that all the files are kept in the assets directory and copied over to the public via gulp. The reason behind NOT using CDN's here was because I wanted to keep the integrity of the app/design/style for years to come. Using the specific stylesheets/scripts and not referencing a CDN meant that I could be 100% sure that the app itself would contain all it needed to survive. That does however take up disk space and ultimately weighs down the app with files that COULD be kept off-site. And for an app that prides itself on minimalism, this is something I've put thought into.Curious to know anyones' thoughts on this and if someone who is very design-oriented/capable wants to take a stab at re-organizing the resource assets, I'd be excited to see what you could come up with.
Biggest stipulation here: The app needs to look/feel as it does in it's current state. Anything from animations to the styling needs to be consistent and be full-proof for future downloads. I know it's a big task, but you guys have already proven to be quite capable when it comes to helping out with this, so have at it. :)
The text was updated successfully, but these errors were encountered: