- Assets user guide
- AEM 6.4 Assets release notes
- About DAM
- User experience improvements
- Best practices for assets
- Use AEM Assets
- Dynamic Media
- Dynamic Media Newsletter by Experience League
- Setting up Dynamic Media
- Working with Dynamic Media
- Configuring Dynamic Media - Scene7 mode
- Configuring Dynamic Media - Hybrid mode
- Troubleshooting Dynamic Media - Scene7 mode
- Managing Dynamic Media assets
- Best practices for optimizing the quality of your images
- Managing Dynamic Media Viewer Presets
- Applying Dynamic Media Viewer Presets
- Managing Dynamic Media Image Presets
- Applying Dynamic Media Image Presets
- Dynamic Media Video Profiles
- Dynamic Media Image Profiles
- Smart Imaging
- Video
- Adding Scene7 features to your page
- HTTP2 delivery of content
- Delivering Dynamic Media assets
- Activating hotlink protection in Dynamic Media
- Image Sets
- Mixed Media Sets
- Spin Sets
- Panoramic Images
- Video
- Interactive Images
- Interactive Videos
- Carousel Banners
- Using Quickviews to create custom pop-ups
- Delivering optimized images for a responsive site
- Previewing Dynamic Media assets
- Adding Dynamic Media assets to pages
- Embedding the Dynamic Video or Image viewer on a web page
- Linking URLs to your web application
- Using Rulesets to transform URLs
- Publishing Dynamic Media assets
- Invalidating your CDN cached content
- Installing Feature Pack 18912 for bulk asset migration
- Working with Selectors
- Extend Assets
- Administer Assets
- Assets supported formats
- Search facets
- Managing Metadata for assets
- XMP writeback to renditions
- Asset link sharing
- Asset reports
- Enhanced Smart Tags
- Profiles for processing metadata, images, and videos
- Cascading metadata
- Create and configure Asset Editor pages
- Assets sizing guide
- Metadata Schemata Reference
- Best practices for translating assets efficiently
- Assets performance tuning guide
- How to edit or add metadata
- Assets migration guide
- XMP metadata
- Assets network considerations
- AEM Assets vs. AEM MediaLibrary
- Using PDF rasterizer
- Configuring asset upload restrictions
- AEM and Creative Cloud integration best practices
- Integrating AEM Assets with InDesign server
- Metadata profiles
- Digital Rights Management in Assets
- Using demo package for Asset Insights
- Assets Offloading Best Practices
- Assets file format best practices
- Assets Monitoring Best Practices
- Camera Raw Support
- Detecting MIME Type of Assets Using Apache Tika
- Imaging Transcoding Library
- Support for IPTC Metadata
- Metadata Schemas
- Multi-tenancy for Collections, Snippets, and Snippet Templates
- Watermarking
- Bulk Metadata Import and Export
- Asset Templates
- AEM to Creative Cloud Folder Sharing Best Practices
- Folder Metadata Schema
- Managing Smart Tags
- Brand Portal
- Content Fragments
- Working with Content Fragments
- Managing Content Fragments
- Content Fragment Models
- Variations - Authoring Fragment Content
- Content Fragment Associated Content
- Metadata - Fragment Properties
- Content Fragments - Delete Considerations
- Content Fragments - Markdown
- Creating translation projects for Content Fragments
- Manage Assets
- Managing Assets with the Touch-Optimized UI
- Managing multiple assets and collections
- Asset selector
- Managing Collections
- Check in and check out files in Assets
- Configure asset tagging using the Smart Content Service
- Enabling duplicate detection
- Enhanced sorting of assets in AEM
- Organize digital assets
- Managing video assets
- Creating Translation Projects
- Preparing Assets for Translation
- Download assets from AEM
- Asynchronous Operations
- Lightbox
- Enabling Asset Insights through DTM
- Configuring Asset Insights
- Applying translation cloud services to folders
- Using Page Tracker and Embed code in web pages
- Managing Compound Assets
- Related Assets
- Asset Insights
- Searching Video Assets
- Private folder sharing
- Smart Content Service Training Guidelines
- Video renditions
- 3D Assets
- AEM 3D release notes
- Working with 3D assets
- Installing and configuring AEM 3D
- Advanced configuration settings
- Working with Adobe Dimension assets
- About the uploading and processing of 3D assets in AEM
- Resolving file dependencies
- Viewing 3D assets
- Rendering 3D assets
- About the use of stages in AEM 3D
- Setting up a standard stage with Autodesk Maya and Mental Ray
- Working with the 3D Sites component
- Integrating AEM 3D with Autodesk Maya
- About working with IBL stages
- Integrating AEM 3D with Autodesk 3ds Max
- Setting up an IBL stage with Autodesk Maya and Mental Ray
HTTP2 Delivery of Content
Adobe is excited to announce the availability of HTTP/2 delivery of content with the overall benefit of improved performance.
What is HTTP/2?
HTTP/2 improves the way browsers and servers communicate, allowing for faster transfer of information while reducing the amount of processing power that is needed.
The following website describes HTTP/2 and its beneifts in a brief and simple manner:
https://www.engadget.com/2015/02/24/what-you-need-to-know-about-http-2/
What are the key benefits of moving to HTTP/2 for content delivery?
Performance improvement varies widely based on factors such as your website’s code, how you are using Dynamic Media, the consumer’s device, screen and location, and so on.
Adobe’s own testing yielded the following results:
- For images, response time improved 7%-28% depending on device and browser. The most notable performance gains were on iOS devices.
- For viewers, load time performance improved up 15%.
The following demonstration illustrates the difference between HTTP/1 versus HTTP/2 loading:
Am I eligible to switch over to HTTP/2?
To use HTTP/2, you must meet the following requirements:
-
Use secure HTTPS for your rich media requests.
-
Use the Adobe-bundled CDN (content delivery network) as part of your Dynamic Media license.
-
Use a dedicated (non- company-h.assetsadobe#.com) domain.
If you already have a dedicated domain, you can opt-in by way of Technical Support.
If you do not have a dedicated domain, Adobe will schedule your transition to HTTP/2 in 2018.
What is the process for enabling HTTP/2 for my Dynamic Media account?
You must initiate the request to switch over to HTTP/2; it is not automatically done for you.
-
Initiate a Technical Support request to switch over to HTTP2. See Accessing the AEM Support Portal.
-
Provide the following information in your support request:
- Primary contact name, email, phone.
- All domains to be transitioned over to HTTP2.
- Verify you are using secure HTTPS for rich media requests.
- Verify you are using the CDN through Adobe and are not managed with a direct relationship.
- Verify you are using a dedicated domain. If you use Dynamic Media, then you already are using a dedicated domain.
-
Technical Support will add you to the HTTP/2 customer waitlist based in the order in which requests were submitted.
-
When Adobe is ready to handle your request, support will contact you to coordinate the transition and set a target date.
-
You will be notified after completion and can verify successful transition over to HTTP2.
Because the browser does not state this fact, it is necessary to download an extension.
For Firefox and Chrome there is an extension called “HTTP/2 and SPDY Indicator”. Browsers only support http/2 securely, so it is necessary to call a URL with https to verify. If http/2 is supported, this is indicated by the extension in the form of a blue Flash symbol, and a header “X-Firefox-Spdy” : “h2”.
-
When can I expect to be transitioned over to HTTP/2?
Requests will be processed in the order in which they are received by Technical Support.
There may be a long lead time because the transition to HTTP/2 involves clearing the cache. Therefore, only a few customer transitions can be handled at a time.
What are the risks with moving to HTTP/2?
The transition to HTTP/2 clears out your cache at the CDN because it involves moving to a new CDN configuration.
The non-cached content directly hits Adobe’s origin servers until the cache is rebuilt again. Because of this, Adobe plans to handle a few customer transitions at a time so that acceptable performance is maintained when pulling requests from our origin.
How can you verify whether a URL or website is activated with HTTP/2?
Because the browser does not state this fact, it is necessary to download an extension.
For Firefox and Chrome there is an extension called “HTTP/2 and SPDY Indicator”. Browsers only support http/2 securely, so it is necessary to call a URL with https to verify. If http/2 is supported, this is indicated by the extension in the form of a blue Flash symbol, and a header “X-Firefox-Spdy” : “h2”.