Thanks for making CIRCUIT 2016 Great!
Did you miss CIRCUIT 15, too? You're in luck, the link below takes you to video of all CIRCUIT 15's presentations!
Content authors face an increased demand to leverage data to improve the experiences they deliver and to build personalized content for an increasingly fragmented audience landscape. With version 6.2 Adobe Experience Manager continues to deepen its integration with Adobe Marketing Cloud solutions and core services like Adobe Target, Adobe Analytics and DTM.
Even basic AEM deployment involves some network communication. All services need to be aware of each other to make the entire AEM stack usable for both content editors and end users. During my talk I'll present how Cognifide combined Consul (www.consul.io) and Chef (www.chef.io) to: - make sure AEM always talk to correct endpoint, no matter how many instances of given service we run - no longer think about hardcoding IP addresses into AEM configs or Chef cookbooks - automatically pick up new services as they go online, and more.
CIRCUIT's Day 1 lunch is sponsored by AEM Mobile! Join Mike Zahorik in the White ballroom to hear about AEM Mobile before it feeds into our first post-lunch session.
We've been busy open-sourcing much of our support infrastructure around AEM. We'll be giving an overview of what we've published, discuss how and why to use them, as well as some of the technology/architecture used.
Being able to scale an application in the cloud isn’t only about the application or the cloud environment themselves, but mostly about automating everything. Many AEM projects are solely focussing on the fronted and the authoring processes, but don’t focus on processes, which enables the organization to run this application at scale. This means, that manual deployments, manual configuration, grepping log files for success or failure messages, changing ACLs manually and so on are still default processes when the application is delivered. While this already creates a lot of work with smaller installations, you cannot run dozens or hundreds of AEM instances using this approach. Automation is the only solution to this problem. While there’s no pre-backed solution for it yet, a lot of individual bits and pieces are already available, but not commonly used. But its not only the deployment aspect. Many applications itself rely often on someone log in as „admin“ and fix something, if a process goes wrong or a workflow is stuck. This approach is also flawed both from a notification point of view (do you want users of the systems to call in to report a problem?) and from a scaling point of view. So many processes need a much better error handling, so that the system is capable of "healing itself“. Or there must be a notification which enables the admin to fix the problem immediately after occurring, so your users don’t call.
Learn about the new AEM Communities product and it's scalable frameworks that can be leveraged to build rich experiences for your users.
IoT realized through AEM and AWS
We have a great spot on the Park Grill Plaza on Wednesday night after day 1 of sessions to relax, have a drink and a bite, and mingle with other attendees and speakers. We have an open air tent with bags sets and ping pong right under the The Bean (or Cloudgate if you want to go by official names) Park Grill Plaza is just kitty corner from the Chicago Athletic Association. See you there!
Chef in the Cloud!
With advent of modern infrastructure patterns and cloud, CDNs have become an integral part of website delivery. CDNs provide unlimited scale without the need to provision expensive infrastructure and increased complexity. CDN Caching has become an important component of modern architecture.
Giving content authors the tools they need to successfully manage an individual website within an AEM instance that contains multiple sites is the ultimate goal. As frontend developers, we use custom AEM components to extend functionality, to ensure that content is rendered consistently sitewide, and to provide a reliable HTML structure to style content responsively. In this presentation we’ll explain a frontend development approach to designing components for multitenancy including the following topics: * Benefits and pitfalls to multitenant components * Building a base bundle of components with generic styles and extending them with brand bundles * How to determine whether to add configuration options to an existing component or create a new one * Managing design expectations with the flexibility of a CMS
By adapting tools intended to generate SVG sprites as part of a front end automation workflow to instead generate Sightly Template files, we can inline SVGs into our component templates without duplicating the code or having to manually manage the it. In modern browsers, inline SVG builds on the advantages of SVG by exposing the elements within the graphic to CSS, including transitions, allowing us to create rich interactions very easily. With some light IE polyfills, we can even apply transforms, and, if we need to support legacy browsers, we can fall back on the original functionality of the sprite builders and include fallback definitions to SVG or PNG sprites in our Sightly templates and CSS. This talk will focus on Gulp, but the concepts can be applied to most common automation tools.
I will review how Iron has helped my team develop quickly and with less ramp up time for new developers.
The industry is moving to container based deployments and monolithic applications are split up into separately runnable smaller pieces, microservices. In this session we will explore how to run AEM in such a world and how to independently scale different parts of the architecture. OSGi and Apache Sling provide an ideal foundation for deploying and running functional parts in separate containers as microservices. These services can be used to build an IoT solution. The session will end with a demo where an IoT device consumes the microservice live on stage.
This session will be an overview of the sightly templating language. It will cover why one should begin using sightly, how to begin, what are some of the more commonly used tags, and a little about display contexts.
While AEM Solr Search provides a framework for indexing and searching content within AEM, it does not address other real-world use cases such as indexing and searching content external to AEM (i.e. products). Secondly, it assumes that the final indexable AEM document will be produced entirely by AEM. This is often not the case, as advanced search applications typically need to enrich the document prior to indexing using external data sources.
In this talk we will extend the AEM Solr Search reference architecture to include document processing capabilities using Apache Camel. As an example, two real-world use cases will be provided: 1) ingesting an external product data set via Apache Camel into a shared Solr instance and delivering the results via AEM, and 2) enriching AEM content with analytics and ratings data for the purpose of applying popularity boosting.
This talk is about how Zebra + ICF Olson partnered to develop a marketing tool, the Zebra Media Library, on top of our 5.6.1 version of the DAM. Leveraging powerful open source tools like SOLR, the Zebra Media Library provides a real-time interface for employees and marketing agencies to download ~20,000 Zebra branded assets for the the sales, marketing, and technical support of our extensive product lines. The tool features integrations for the DAM with SSO, SOLR, SAVO, and more on the way. It’s a custom tool designed, implemented and supported by an in-house Zebra + ICF team and we’re excited to tell you how this tool was born and continues to grow with each sprint.
The AEM Touch UI has been built to allow for extensive customization. This can be very useful especially when out of the box admin screens don't provide exactly what you need. Perhaps your project integrates with external systems such as databases, AWS, IoT or other 3rd party services that may or may not have their own admin consoles. And even if they do, maybe they are not intuitive or you would rather have all control in one place. This talk will take you through a real world scenario of building a custom Touch UI admin screen to increase productivity.
We'll demonstrate how simple it is to begin building model-based components in addition to discussing more complex usages of the Sling Models API, such as custom injectors, Sightly templates, testing, and debugging.