Assets/Meta consistency.

[lucalanca]

Assets files

There are three types of files:

Content Assets

• Images, videos, audios, etc.
• These files are part of the content (and so, they should live under content/.
• We want to (optionally) group these files together in whatever format we think it's best for a specific project. E.g.: content/images, content/videos.
• We want these files to be saved under build/assets/. E.g.: content/images/content-image.svg should be saved under build/assets/images/content-image.svg).
• We want these files to be rev'd when building for production.

Design Assets

• Images, videos, audios, etc. These files are very thigh to the code/design of the project (not the content)
• These files should live under assets/.
• We want to (optionally) group these files together in whatever format we think it's best for a specific project. E.g.. assets/images/, assets/videos.
• We want these files to be saved under build/assets/. E.g.: assets/images/content-image.svg should be saved under build/assets/images/design-image.svg).
• We want these files to be rev'd when building for production.

Meta Assets

• robots.txt, .htaccess, favicons, manifest.json, etc
• These files should live under assets/meta.
• We want these files to be saved under the root of the build folder: build/.
• We DON'T want these files to be rev'd on production, as their name is a convention.

What this PR does:

• Separates assets and meta tasks. Assets (content assets AND design assets) need to be rev'd so they need to share the same pipe. Meta: don't need any special pipe, they just need to get copied to the build folder.
• Assets is now only one stream, instead of 4. We can add new folders within assets and we don't need to add a new stream for this filetype. In other words, any asset/:type and content/:type is allowed. E.g.: assets/images and content/images.

I think this organisation is a more scalable solution that what we currently have. For more than once, I had the need to create a new stream for a new file type. With this, we don't need to do it. Furthermore, I think this is more maintainable as there exists only 1 stream for all assets (regardless if it is a "content asset " or a "design asset").

[meodai]

I like! A little bonus could be to actually image-optim the favicon if there are any?

[lucalanca]

Ok, we discussed this topic a little bit further and here's the final proposal of this PR:

Design Assets

They should go under src/materials/icons (or any other file). They should get rev'd and their reference changed on both .css and .html files.

Content Assets

They should go under content/{images,videos,etc}. They should get rev'd and their reference changed on both .css and .html files.

Meta Assets

They should go under src/meta. They never get rev'd and they will end up at the root of the build folder.