Assets in the cloud with Neos 2.0 & Flow 3.0

45
Assets in the Cloud with Neos 2.0 & Flow 3.0

Transcript of Assets in the cloud with Neos 2.0 & Flow 3.0

Page 1: Assets in the cloud with Neos 2.0 & Flow 3.0

Assets in the Cloudwith Neos 2.0 & Flow 3.0

Page 2: Assets in the cloud with Neos 2.0 & Flow 3.0

What the Asset?

Page 3: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 4: Assets in the cloud with Neos 2.0 & Flow 3.0

WebserverDatabaseShared Filesystem

Page 5: Assets in the cloud with Neos 2.0 & Flow 3.0

WebserverDatabaseCloud Storage

Page 6: Assets in the cloud with Neos 2.0 & Flow 3.0

WebserverDatabaseCloud Storage

Page 7: Assets in the cloud with Neos 2.0 & Flow 3.0

WebserverDatabaseCloud Storage

Page 8: Assets in the cloud with Neos 2.0 & Flow 3.0

WebserverDatabaseCloud StorageDropbox / GDrive

CDN

Page 9: Assets in the cloud with Neos 2.0 & Flow 3.0

ON

Page 10: Assets in the cloud with Neos 2.0 & Flow 3.0

Building Blocks

Page 11: Assets in the cloud with Neos 2.0 & Flow 3.0

ResourceA resource is the atom of assets; it is the representation of data which is usually stored as a file. It is best practice to not share Resource objects between multiple parents.

Page 12: Assets in the cloud with Neos 2.0 & Flow 3.0

Resource PointerThere are NO Resource Pointer objects anymore in Flow 3.0.

Page 13: Assets in the cloud with Neos 2.0 & Flow 3.0

Static vs PersistentStatic resources are deployed as part of the code base. They never change during runtime. Persistent resources is data uploaded, created or imported by the application. Each resource is registered in the database.

Page 14: Assets in the cloud with Neos 2.0 & Flow 3.0

StorageResources are stored in internal storages which are only accessible to your application. There are writeable and read-only storages.

Page 15: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 16: Assets in the cloud with Neos 2.0 & Flow 3.0

Publishing TargetResources are published to Publishing Targets. The Publishing Target provides a public URL to a single or multiple resources.

Page 17: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 18: Assets in the cloud with Neos 2.0 & Flow 3.0

CollectionEach resource belongs to one collection. A collection defines the storage and publishing target to use for the contained resources.

Page 19: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 20: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 21: Assets in the cloud with Neos 2.0 & Flow 3.0

Common Tasks

Page 22: Assets in the cloud with Neos 2.0 & Flow 3.0

Publish to a CDN

Page 23: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 24: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 25: Assets in the cloud with Neos 2.0 & Flow 3.0

Import a PDF file

Page 26: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 27: Assets in the cloud with Neos 2.0 & Flow 3.0

Upload an image

Page 28: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 29: Assets in the cloud with Neos 2.0 & Flow 3.0

Get a URL for a resource

Page 30: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 31: Assets in the cloud with Neos 2.0 & Flow 3.0

Media

Page 32: Assets in the cloud with Neos 2.0 & Flow 3.0

Asset

Image

Audio

Document

Video

Image Variant

Crop Adjustment

B/W Adjustment

Thumbnail

Page 33: Assets in the cloud with Neos 2.0 & Flow 3.0

What else?

Page 34: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 35: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 36: Assets in the cloud with Neos 2.0 & Flow 3.0

S3 / WebDAV / GDrive …

Page 37: Assets in the cloud with Neos 2.0 & Flow 3.0

CSS path rewriting

Page 38: Assets in the cloud with Neos 2.0 & Flow 3.0

Filters

Page 39: Assets in the cloud with Neos 2.0 & Flow 3.0

one more thing …

Page 40: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 41: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 42: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 43: Assets in the cloud with Neos 2.0 & Flow 3.0
Page 44: Assets in the cloud with Neos 2.0 & Flow 3.0

more details? questions?

Page 45: Assets in the cloud with Neos 2.0 & Flow 3.0

[email protected] www.flownative.com

@robertlemke

share your thoughts