More than two years in the making, the new cloud-capable asset management finally is available in Flow 3.0 and Neos 1.3. With its companion, the new Media package, it provides a sophisticated but easy-to-use API for developers to manage media assets. In this session you'll learn how to create and manipulate images, use local and remote storages, publish to Content Delivery Networks and even create your very own storage and publishing solutions.

1. Assets in the Cloud
by Robert Lemke

2. What the Asset?

4. Webserver
Database
Shared Filesystem

5. Webserver
Database
Cloud Storage

6. Webserver
Database
Cloud Storage

7. Webserver
Database
Cloud Storage

8. Webserver
Database
Cloud Storage
Dropbox / GDrive
CDN

9. O
N

10. Building
Blocks

11. Resource
A 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.

12. Resource Pointer
There are NO Resource Pointer
objects anymore in Flow 3.0.

13. Static vs Persistent
Static 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.

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

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

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

21. Common Tasks

22. Publish to a CDN

25. Import a PDF file

27. Upload an image

29. Get a URL for a
resource

31. Media

32. Asset
Image
Audio
Document
Video
Image Variant
Crop Adjustment
B/W Adjustment
Thumbnail

33. What else?

36. S3 / WebDAV / GDrive …

37. CSS path rewriting

38. Filters

39. robert@flownative.com
www.flownative.com
@robertlemke
share your thoughts