gevonden over assets:
Assets Defined
Before looking at a way to actually organize our assets, I think it’s worth trying to come up with a working definition of what a project asset actually is. In our case, we’re going to be talking about WordPress-specific projects (so this will vary if you’re working in another environment).
First, the official definition of asset is:
"a useful or valuable thing, person, or quality.
So using this as a guideline for our work can help. As previously mentioned, CSS, JavaScript, images, fonts, and so on can all be considered assets. Therefore, would it not make sense to have a top-level assets directory into which all of the above would live?
Alternatively, couldn’t a case be made that a given library has its own set of assets? For example, think of a front-end framework that includes glyphs, fonts, images, and CSS. Would an assets subdirectory make since under a lib directory?"
---in een asset-folder wordt dit kennelijk ondergebracht, dus .
ik denk dat met "to crop" (a film) wordt bedoels "inkorten":
bijv. voor TV-uitzendingen moe(S)ten vaak films worden ingekort om ruimte te maken voor reclame ecc. en om te passen in de TV-tijd-schema's. Weinig films dus die je op TV ziet zijn dus oorspronkelijke versies.
