EVOLVE&#x27;15 | Flash Brief | Cat Reusswig | Adventures in AEM Upgrades

Presented at 3|SHARE's EVOLVE'15 - The Adobe Experience Manager Community Summit on Monday August 17th, 2015 at the Hard Rock Hotel in San Diego, CA. http://evolve.3sharecorp.com

Technology

AUGUST 17, 2015
Cat Reusswig, Senior Director, Web Portals Engineering, Time Warner Cable

2
 How to begin?
 What should the MVP be?
 How do we roll it out?
AGENDA: ADVENTURES IN UPGRADING

3
We started with one
scrum team focused on
driving the key
recommendations to
make regarding the
architecture changes
offered in 6.0
HOW TO BEGIN?
Mongo? Oak? Solr? Ours?.........

4
Began to build a
roadmap of tasks and
key work items to
investigate
GETTING STARTED
The long road ahead…

5
 TarMk vs Mongo?
 Mongo for authors if TarMk seems favorable for
pubs?
 Java8 upgrade?
 New clean vs upgrade in place?
 6.0 vs 6.1?
 How to handle all the API version updates?
 How will teasers work in 6.0?
 jQuery upgrade – how far to clean up old?
 Google guava 15 vs 17…
 Classic UI vs Touch UI?
 When to start using Sightly?
DRIVING OUT THE QUESTIONS TO ANSWER
Inventoring the journey…

6
TRYING THINGS WORKS BEST
#datadrivendecisions

7
1. Bare-bones as-is (as much as we can)
2. 6.1
3. Java8 upgrade
4. Cloud migration = new environments
5. = new deploy process
6. Pre-work: jQuery upgrade & component cleanup
7. Post work: new personalization, Campaign,
TouchUI…
WHAT SHOULD THE MVP BE?
Choices choices choices

8
Lessons learned from 5.6.1 upgrade?
Which TWC site?
Should we do part of a site?
Should we consider a regional roll?
=Twc.com
=Full site
=All regions
HOW TO ROLL IT OUT?

9
 Check the Adobe
docs
 Check the upgrade
scenarios
 Check the Service
Pack info
 Check performance
optimization
 Try things – decide
your path
ALL THE OTHER STUFF YOU GOTTA DO…
Learn, research, experiment, list, test, decide…

Deploy Stack
INFRASTRUCTURE TOOLS
Haproxy
Web Server Web Server
AEM
Master
AEM
Replica
Terraform
Cloud Orchestration
OpenStack
Security Groups
Floating IPStorage/Volumes
DNSPuppet
Keys
Node/VM

BUILD/DEPLOY PIPELINE TOOLS
Jenkins
Job Orchestrator
GitHub
Code Repository
Artifactory
Artifact Repository
Jira
Ticket System
Confluence
Wiki
Deploy
Gradle, Groovy, etc
Build
Gradle, Groovy, etc
App
AEM
AppDynamics
APM Metric Collector
Test
Unit, Functional, Integ
.
HipChat
Notification
Splunk
Log aggregator
Monitoring

12
 TarMk vs Mongo? TarMK for us
 Mongo for authors Active/Passive Author cluster
 Java8 upgrade? YES
 New clean vs upgrade in place? Clean
 6.0 vs 6.1? 6.1
 How to handle all the API version updates?
tackle 1by1
 How will teasers work in 6.0? As is
 jQuery upgrade – how far to clean up old? Work
w the biz
 Google guava 15 vs 17… v15
 Classic UI vs Touch UI? Classic
 When to start using Sightly? Still an IF
THE ANSWERS FOR TWC
Inventoring the journey…

13
• Resolving uber jar issues
• Resolving bundle dependencies
• Testing, testing
• Updating OS Grabbit to work on both 5.6.1 & 6.1
• Syncing the jQuery final details
• Testing our environment build
• Getting ready for UAT in Sept
• Determining our final deploy plan & author freeze
• Getting excited to be DONE!
THE JOYS OF UPGRADING
#where_are_we?

15
Catherine.reusswig@twcable.com
twitter.com/reuscat
linkledin.com/in/catreusswig
Images by:

There is increasing talk of DevTestOps to emphasise that the DevOps promise to release software quickly should not be at the expense of its quality and ultimately of its value. STAMP (Software Testing AMPlification) project can provide you with several powerful test amplification features to be exploited at three different stages in a DevOps process: • automatic generation and execution of variants of existing test cases; • automatic generation of variants of existing test configurations; • automatic generation of test cases from available production logs in order to reproduce and fix any anomaly which may occur. This talk shows you how to use this technology within your production processes in order to increase your software quality.

Gitlab meets Kubernetes

inovex GmbH

Scaling UI5 Projects via Standardized Project & Infrastructure Setup (Ui5Con ...

Nabi Zamani

This document discusses strategies for standardizing UI5 project setup and infrastructure to facilitate scaling UI5 projects. It describes a process for code reviews, testing, and deployment that utilizes GitHub, Gerrit, Jenkins, and ABAP systems. It also lists common challenges faced in UI5 development and provides links to GitHub repositories containing seed projects, components, libraries, and tools to help address these challenges and standardize development practices. The goal is to share knowledge and establish practices that improve collaboration, testing, and deployment across UI5 projects and teams.

Continuous deployment of Rails apps on AWS OpsWorks

Tomaž Zaman

This document discusses continuous deployment of Rails applications on AWS OpsWorks. It begins with introductions and then covers: - Using SCRUM methodology for development - Git workflow with feature branches and pull requests - Tools for monitoring gems (Gemnasium) and code quality (CodeClimate, Travis CI) - An overview of AWS OpsWorks including stacks, layers, apps, and using Chef for automation - How OpsWorks deployments work by pulling from GitHub and running deployment hooks - Other AWS services that can be used like RDS, ElastiCache, S3 - Logging to external services like Loggly - Approaches for running background jobs like Sidekiq -

和艦長一起玩轉 GitLab & GitLab Workflow

Chen Cheng-Wei

This document provides an overview and summary of GitLab and DevOps workflows presented by Cheng Wei Chen at the STUDY4 TW .NET Conf 2019. The key points discussed include: - An introduction to GitLab and its components and architecture. - A comparison of different software development workflows and an explanation of the GitLab Workflow. - A discussion of different Git branching strategies including GitLab Flow. - An overview of GitLab Auto DevOps and how it can automate the DevOps pipeline. - A reiteration of the main topics and a conclusion on how GitLab supports DevOps practices.

Serious deployment: unlimited environments!

Gunnar Wrobel

Dr. Gunnar Wrobel discusses deploying applications to unlimited environments on a per-branch basis using cloud infrastructure as code. By deploying infrastructure and applications for each branch through tools like GitLab CI and CloudFormation, it allows for easy testing, demonstration, and experimentation without impacting production. While there may be some operational overhead in managing many environments, it facilitates collaboration and learning at low cost. Resources like databases and functions are configured specifically for each stage through template parameters and conditions.

Sprachsteuerung mit dem Google Assistant – Add a new User Interface to your P...

inovex GmbH

„Computer, Tee, Earl Grey, heiß“ Jeder Star-Trek-Fan wird dieses Zitat kennen, mit dem Capt. Picard sich regelmäßig sein Lieblingsgetränk replizieren lässt. Die Sprachsteuerung von Computern und Maschinen ist fester Bestandteil vieler Science-Fiction-Szenarien. Daher ist es auch nicht verwunderlich, dass schon mehrere Versuche unternommen wurden, diese Technologie zu etablieren, mit eher durchschnittlichem Erfolg. Allerdings deutet sich aktuell ein großer Fortschritt in der Entwicklung von Sprachsteuerungen an, die sich am deutlichsten in der Inkarnation von Geräten wie Amazon Echo oder Google Home darstellt. In der Session zeigen wir die prinzipielle Funktionsweise einer Sprachsteuerung, die Vergleichbarkeit mit Chatbots, und erweitern einen bestehenden Dienst um ein Voice-User-Interface. Dabei zeigen sich die Besonderheit dieser Benutzerschnittstelle im Vergleich zu grafischen Interfaces und die Herausforderungen, die damit verbunden sind. Event: MobileTech Conference 2017 Datum: 15.03.2017 Speaker: Dominik Helleberg, inovex GmbH Weitere Tech-Vorträge unter https://www.inovex.de/de/content-pool/vortraege/

Continuous delivery the french way Agile Cambridge 2014

Dimitri Baeli

Let’s see what it takes to build an automated testing/QA setup with Kubernetes and GitLab from scratch, using off-the-shelf components. The goal is to automatically deploy any feature-x or hotfix-x branch to individual environments for automated tests and to make it easier to share intermediate results within the team. This talk will touch on abstract topics like continuous delivery, the value of developer tooling and well-defined workflows, before diving deep into implementation details, learnings, gotchas and stuff-which-went-wrong.

Dmytro Kochergin “Autotest with CYPRESS”

Cypress is an open source JavaScript testing framework for testing web applications. It allows for running automated tests directly in the browser without any build step required. Some key features of Cypress include time travel debugging, automatic waiting, running tests headlessly on CI, and generating screenshots and videos. The document discusses using Cypress to test an application and some issues faced, such as tests not restarting on file save and emulating a mobile browser. It provides solutions for some problems like uploading files and handling CORS errors. Overall reproducing test data across environments remains an unresolved challenge.

Introduction cypress

Oim Trust

This document introduces Cypress, an open-source test runner for front-end applications. It is described as fast, easy to use, and reliable for testing anything that runs in a browser. Key benefits highlighted include being fast, open source, working on any front-end framework, being friendly for developers and QA engineers using JavaScript, and having features like time travel and real-time reloading. The document also provides instructions on installing Cypress and running tests using its GUI runner or headless mode.

Ivan Dryzhyruk “Ducks Don’t Like Bugs”

AEGIS-ACCESSIBLE Projects

This document discusses software testing techniques and best practices. It covers test design techniques like equivalence partitioning and boundary value analysis. It emphasizes the importance of tests being fast, isolated, repeatable, self-validating, and thorough. The testing pyramid hierarchy of tests is explained. Test-driven development and various test utilities are also outlined. The conclusions emphasize that tests help increase confidence in code, prevent accidental breaks, and ensure documentation remains relevant.

Continuous Deployment at Kitchensurfing

Lars Kluge

Continuous deployment is the automated process of shipping code to production with every push to the master branch. Some benefits include earlier feedback, faster development, and lower risk of deployments. Kitchensurfing uses continuous deployment with Ruby on Rails, MongoDB, and Heroku. Their process includes code reviews, testing, and automated deployment to Heroku after successful builds. MongoDB helps avoid schema migrations during product development. They emphasize trusting test suites, releasing in small pieces, using feature flags, and observing production after deployments.

How to push a react js application in production and sleep better

Emanuele Rampichini

Aws uk ug #8 not everything that happens in vegas stay in vegas

Peter Mounce

This document discusses various topics related to DevOps practices at different companies: 1. Netflix prioritizes speed of innovation and availability over running costs when developing software. They found this approach ended up costing less than expected. 2. Riot Games uses tools like Chef to deploy their massively multiplayer online game League of Legends to the cloud. This helps them solve launch issues and scale efficiently. 3. Many companies like Netflix, Riot Games, and Kickstarter test new code and configurations in production at a large scale to continuously improve their systems and user experience. 4. Centralized logging services are important for developers to more easily monitor systems, debug issues, and reduce time spent on call

Comparing Agile QA Approaches to End-to-End Testing

Katie Chin

The document compares agile QA approaches like end-to-end testing and discusses how Quid uses both Selenium and RainforestQA for testing. It notes that while Selenium allows for fast automated testing, it is tied to the frontend implementation. RainforestQA uses human testers which is easier to maintain but slower. For complex products like Quid, RainforestQA has scaled testing better and freed up engineer time for more exploratory testing.

reactNative_Android

Penka Simonova

This document summarizes React Native for Android development. It covers mobile development platforms like Android and HTML5, compares technologies for mobile development, and key concepts of React Native like virtual DOM, components, and lifecycle. It also provides instructions for getting started with React Native, discusses components, custom modules, and pros and cons of React Native which include fast development time and performance with live reload.

An almost complete continuous delivery pipeline including configuration manag...

ulfmansson

Smarter deployments with octopus deploy

Thibaud Gravrand

This document discusses Octopus Deploy, a deployment automation tool. It describes Octopus Deploy's architecture and 7 step deployment process. The process includes declaring environments, creating application packages, defining projects, creating deployment processes with steps and variables, releasing packages, and deploying releases to environments. Octopus Deploy supports features like automated deployments, rollbacks, configuration transformations, and integration with build pipelines. It provides visibility through audit logs and manages deployments across development, test, and production environments.

Ethan huang 全民qa

Odd-e

The document describes a new integrated development and testing lifecycle model implemented by a team. The key aspects of the new model include: 1) Breaking down the team silos by having developers involved in all QA activities and the sole tester organizing the entire team. 2) Adopting a new V-model that integrates development and testing rather than using waterfall or iterative waterfall. 3) Requiring representation of requirements using test cases, test-driven development, peer code reviews, continuous integration/testing, and user acceptance testing each iteration to achieve two "quality gates." 4) This new approach resulted in fewer bugs found by the client during testing compared to their previous method.

GNOME Accessibility Testing

The document discusses proposals to improve accessibility testing of GNOME applications. It suggests building a set of accessibility regression tests for each application and component, running these tests at different points in the six-month release cycle, and continuously in a test automation system. Specific proposals include choosing a testing technology, deciding where to store the tests, building and operating a continuous testing system, and writing initial accessibility tests for applications.

GitLab Frontend and VueJS at GitLab

Hot Reloading with React - Experiences

Heribert Schütz

Cloudformation vs terraform_vs_ansible

Geert Theys

How to use any static site generator with GitLab Pages.

Ivan Nemytchenko

sitMUC 2018 - Speed up abap-unit data creation process

Alexander Geppart

How to Upgrade to the Newest Shiniest Django Version

Susan Tan

This document summarizes Susan's presentation on upgrading Django projects. The presentation covered: - Why upgrades are important for getting new features, fixes and security updates. - The steps involved in upgrading include running tests, fixing broken tests one by one, checking that fewer tests fail with each new version, verifying the UI still works, and editing deployment files. - Challenges include dependencies breaking, release notes documenting changes that require code updates, and the repetitive nature of fixing tests across multiple versions. - The key takeaways are to upgrade one version at a time, run and fix tests with each version, read release notes, break tasks into small steps, and use checklists to track progress

Evolution of GitLab Frontend

Continuous deployment

Stephen Donner

The document discusses moving to a continuous deployment model where code is automatically deployed to production after passing tests in order to quickly deliver features and fixes. It acknowledges this will require expanding test coverage, especially of front-end code, maintaining high code quality, and redefining the relationship between development and QA teams. Initial concerns from QA include the need to measure quality and test environments without Selenium tests, but over time the team realized benefits like safer real-world testing and increased collaboration.

Building a Great AEM Team: Time Warner Cable's Journey

iCiDIGITAL

What's hot

Automated Testing Environments With Kubernetes & GitLab

Vladislav Supalov

Dmytro Kochergin “Autotest with CYPRESS”

Introduction cypress

Oim Trust

Ivan Dryzhyruk “Ducks Don’t Like Bugs”

AEGIS-ACCESSIBLE Projects

Continuous Deployment at Kitchensurfing

Lars Kluge

How to push a react js application in production and sleep better

Emanuele Rampichini

Aws uk ug #8 not everything that happens in vegas stay in vegas

Peter Mounce

Comparing Agile QA Approaches to End-to-End Testing

Katie Chin

reactNative_Android

Penka Simonova

An almost complete continuous delivery pipeline including configuration manag...

ulfmansson

Smarter deployments with octopus deploy

Thibaud Gravrand

Ethan huang 全民qa

Odd-e

GNOME Accessibility Testing

GitLab Frontend and VueJS at GitLab

Hot Reloading with React - Experiences

Heribert Schütz

Cloudformation vs terraform_vs_ansible

Geert Theys

How to use any static site generator with GitLab Pages.

Ivan Nemytchenko

sitMUC 2018 - Speed up abap-unit data creation process

Alexander Geppart

How to Upgrade to the Newest Shiniest Django Version

Susan Tan

Evolution of GitLab Frontend

What's hot (20)

Automated Testing Environments With Kubernetes & GitLab

Dmytro Kochergin “Autotest with CYPRESS”

Introduction cypress

Ivan Dryzhyruk “Ducks Don’t Like Bugs”

Continuous Deployment at Kitchensurfing

How to push a react js application in production and sleep better

Aws uk ug #8 not everything that happens in vegas stay in vegas

Comparing Agile QA Approaches to End-to-End Testing

reactNative_Android

An almost complete continuous delivery pipeline including configuration manag...

Smarter deployments with octopus deploy

Ethan huang 全民qa

GNOME Accessibility Testing

GitLab Frontend and VueJS at GitLab

Hot Reloading with React - Experiences

Cloudformation vs terraform_vs_ansible

How to use any static site generator with GitLab Pages.

sitMUC 2018 - Speed up abap-unit data creation process

How to Upgrade to the Newest Shiniest Django Version

Evolution of GitLab Frontend

Similar to EVOLVE'15 | Flash Brief | Cat Reusswig | Adventures in AEM Upgrades

Continuous deployment

Stephen Donner

Building a Great AEM Team: Time Warner Cable's Journey

iCiDIGITAL

Flavius Ștef: Big Rewrites Without Big Risks at I T.A.K.E. Unconference

Mozaic Works

This document discusses strategies for incrementally rewriting software architecture without big risks. It suggests splitting large rewrites into smaller chunks and using techniques like faking functionality until it is implemented, incremental refactoring, and rewriting in small bites. Specific strategies discussed include researching prerequisites, creating proofs of concept, adding unit and performance tests incrementally, and removing dependencies one by one. Choosing the right refactoring is important, and catalogues of refactorings can provide guidance. An incremental process of analyzing, planning, refactoring, testing and integrating changes in small batches is recommended to validate progress toward goals at each step.

Big rewrites without big risks

Flavius Stef

EVOLVE'16 | Keynote | Cat Reusswig | Taking Your AEM Implementation to The RO...

Innovate Better Through Machine data Analytics

Hal Rottenberg

Scaling Up Lookout

Lookout

The speaker discusses how Lookout has scaled its engineering organization and technical infrastructure over time. In 2011, Lookout had problems with unreliable deployments and a monolithic codebase. It introduced new tools like JIRA, Jenkins, and Git/Gerrit to improve its workflow. It also automated deployments and now has a much higher success rate. As Lookout has grown, it has moved to a more distributed architecture with over 100 microservices running on different technologies. Scaling organizational knowledge and coordinating many independent services will be ongoing challenges.

OSGI,

James Governor

This document discusses OSGi trends, directions, and opportunities. It summarizes that OSGi grew out of a need for modular Java applications but modularity was an afterthought. It is now used widely by companies like Eclipse, IBM, Oracle, and VMware. While OSGi offers benefits, some argue it is still difficult for developers to use. However, as packaging and deployment of applications becomes more distributed and complex, OSGi's modular architecture is increasingly relevant and may see more widespread adoption.

DevOps at Obama for America(2012) and the DNC (DevOps Days NYC Jan 2013)

John Schneider

1) DevOps practices were implemented at the Democratic National Committee between 2009-2011 to improve systems, including virtualization, documentation, version control, automation, and making everything highly available. 2) Early agile development practices and use of AWS services like EC2 and continuous integration helped scale applications for the DNC. 3) Lessons from 2010 were applied in 2012, including use of big data, evaluating hardware vs AWS costs and limitations, and developing analytics tools for various teams.

Sai devops - the art of being specializing generalist

Odd-e

Devops aims to bring developers and operations teams together to collaborate more closely. As systems become more complex, the traditional separation of duties has caused issues with deployment, configuration, and monitoring. By integrating development and operations work, organizations can deploy code changes more rapidly and reliably while improving system performance, security, and availability. Effective devops processes include continuous integration, automated testing of infrastructure changes, configuration management, and monitoring systems in production.

Dean4j@Njug5

ทวิร พานิชสมบัติ

The document discusses various Platform as a Service (PaaS) technologies including Amazon Web Services, Google App Engine, and Microsoft Live Mesh. It notes that these services allow developers to avoid maintaining their own infrastructure and focus on their applications instead. The document also covers JavaFX, a new platform from Sun Microsystems that aims to enable rich user experiences across devices using Java technologies.

Adopt openjdk and how it impacts you in 2020

George Adams

AdoptOpenJDK is rapidly becoming a leading provider of OpenJDK™ binaries. With over 125 million downloads in the last year, it is now a serious contender for your production usage of Java™. AdoptOpenJDK provides prebuilt OpenJDK™ binaries from a fully open-source set of build scripts and infrastructure. This talk will cover how we build on over 15 different platforms, execute over 60,000 tests and distribute OpenJDK™ binaries to millions of users. We will also cover how AdoptOpenJDK binaries compare against the Java™ binaries that you use today. If you’re curious to understand more about our future roadmap, security and supporting platforms like Lego® Mindstorms® then this is the talk for you!

Neotys PAC - Stijn Schepers

Neotys_Partner

Neotys organized its first Performance Advisory Council in Scotland, the 14th & 15th of November. With 15 Load Testing experts from several countries (UK, France, New-Zeland, Germany, USA, Australia, India…) we explored several theme around Load Testing such as DevOps, Shift Right, AI etc. By discussing around their experience, the methods they used, their data analysis and their interpretation, we created a lot of high-value added content that you can use to discover what will be the future of Load Testing. You want to know more about this event ? https://www.neotys.com/performance-advisory-council

DevOps: The New Face Of Application Development - Global Azure Bootcamp

Richard Harbridge

Running distributed tests with k6.pdf

LibbySchulze

Interoperable Clouds and How to Build (or Buy) Them

Mark Voelker

This document summarizes a presentation about interoperability between OpenStack and other open source infrastructure projects like Kubernetes. It discusses how the OpenStack Interoperability Working Group defines guidelines for compatibility between different OpenStack distributions. While no distribution will be identical, following these guidelines ensures core capabilities are supported across approved implementations. It encourages selecting technologies based on common interfaces like APIs, Terraform, or Kubernetes rather than any single vendor implementation to avoid lock-in and allow flexibility.

Apcera Case Study: The selection of the Go language

Derek Collison

Derek Collison, founder of Apcera, discusses why the company selected Go as its primary programming language over other options like Ruby and Node.js. Some key reasons included Go's built-in support for concurrency, its static typing and compilation which aids dependency management, and its suitability for building distributed systems. While Go had some immature areas like its garbage collection and standard library, its focus on stacks, statically linked executables, and ease of learning made it the best choice for Apcera's cloud platform needs. Collison believes more companies will make the same choice as Go continues to evolve and address open issues.

The future of paas is serverless

Yan Cui

Lambda is the next stage in the evolution of the AWS platform. It allows you to build reactive, event-driven systems that are easy to deploy, update and scale. Amazon manages all the undifferentiated heavy-lifting for you so you can focus on delivering value to your customers with even greater speed and cost efficiency. Join Yan in this talk as we take a deep dive through AWS Lambda and the Serverless framework. We'll see how to start building reactive systems using AWS Lambda, Kinesis and API Gateway, without having to manage any servers. And, you only pay for your services when they are used. We'll discuss lessons learned, best practices and current limitations with AWS Lambda. We'll also get to know the Serverless framework, which helps automate both deployment and versioning so that you can better focus on the things that matter to your customers.

In cluster open source testing framework - Microservices Meetup

Neil Gehani

Entrepreneurship3

Yenwen Feng

This document summarizes the experiences of Feng Yanwen in technology entrepreneurship. It discusses the companies he has founded, including Willmobile, and the lessons learned around development processes, tools, scalability, hosting, and entrepreneurship. Key points include choosing the right framework for a project, using agile development methods, planning for scalability from the start, and understanding burn rate and operations costs when starting a business.

Similar to EVOLVE'15 | Flash Brief | Cat Reusswig | Adventures in AEM Upgrades (20)

Continuous deployment

Building a Great AEM Team: Time Warner Cable's Journey

Flavius Ștef: Big Rewrites Without Big Risks at I T.A.K.E. Unconference

Big rewrites without big risks

EVOLVE'16 | Keynote | Cat Reusswig | Taking Your AEM Implementation to The RO...

Innovate Better Through Machine data Analytics

Scaling Up Lookout

OSGI,

DevOps at Obama for America(2012) and the DNC (DevOps Days NYC Jan 2013)

Sai devops - the art of being specializing generalist

Dean4j@Njug5

Adopt openjdk and how it impacts you in 2020

Neotys PAC - Stijn Schepers

DevOps: The New Face Of Application Development - Global Azure Bootcamp

Running distributed tests with k6.pdf

Interoperable Clouds and How to Build (or Buy) Them

Apcera Case Study: The selection of the Go language

The future of paas is serverless

In cluster open source testing framework - Microservices Meetup

Entrepreneurship3

More from Evolve The Adobe Digital Marketing Community

Evolve 19 | Sarah Xu & Kanika Gera | Adobe I/O - Why You Need it to Execute o...

Evolve 19 | Upen Manickam & Amanda Gray | Adventures in SPA with AEM 6.5

This document discusses a project to modernize two separate portals for a client into a single-page application (SPA) using Adobe Experience Manager (AEM) 6.5. The project involved using SPA to display product information and documents, creating an entitlements management screen in AEM author for permissions, and developing mobile apps. Key aspects included upgrading from AEM 6.4 to 6.5 to address SPA issues, integrating with Okta for authentication, and enabling offline viewing capabilities in the mobile apps. The presentation provides details on implementing the SPA, entitlements management, and mobile apps, and discusses challenges overcome around responsive design, permissions, and offline access.

Evolve 19 | Ameeth Palla | Adobe Asset Link - Use Cases and Pitfalls to Avoid

Evolve 19 | Giancarlo Berner | JECIS 2 - The Beginning of a New Era in Buildi...

AEM is content-centric, so is the future of building commerce experiences. In this session, you will be shown how to build modern commerce experiences with AEM. The demo will explain how authors create/configure multiple (industry-independent) stores, configure the commerce environment for each store and manage all the commerce content and features, without writing a line of code. The second part will demonstrate how developers create templates, components, and functionality to build a compelling Web/User/Commerce Experience.

Evolve 19 | Paul Legan & Kristin Jones | Anatomy of a Solid AEM Implementatio...

Evolve 19 | Rabiah Coon & Rebecca Blaha | Rockstar Kickoffs for AEM Projects

The roles of the Product Owner, Business Analyst and/or Subject Matter Expert are crucial to the success of an AEM project, especially at critical times. From the development team’s perspective leveraging these resources during kickoff can set the project up for success. Hear more about the right resourcing and preparation for kickoff can enable development teams to start a project off right and to avoid costly changes (scope increase or rework) later in the project.

Evolve19 | Nick Panagopoulos | World Focus: Translation Tips and Trends

This document summarizes translation tips and trends from a presentation. It includes tips from various companies on testing machine translation and AI, automating tracking and reporting to decrease turnaround times by 50%, and automating file pushing to translate content into 14 languages within a year. It also notes to prepare for unexpected translation spikes by using internal and external translation teams. The document contains charts and graphics on GlobalLink customers and processes.

Evolve 19 | Rabiah Coon, Sabrina Schmidt & Noah Linge | Industry Focus | Furn...

When Furniture Row decided to leave their digital assets management provider to go to AEM, they began a multi-phased journey that has resulted in the transition of their eCommerce platform and content management system. They recently launch a newly redesigned DenverMattress.com site which introduces a headless implementation of AEM sites, a new authoring experience for their content team, and an upgrade from a freestanding instance of Scene7 Classic to Dynamic Media integrated with AEM Assets. Hear from the implementation team and learn more about Furniture Row’s digital evolution.

Evolve 19 | Carl Madaffari | Best Practices | From Customer Data to Customer ...

Today’s customers expect relevant and personalized engagement with brands – or they go elsewhere. In this session, Carl will lay out some of the hurdles involved in crafting a customer- and loyalty-forward data management and architectural strategy. Using examples from specific client engagements, he will outline approaches to building an actionable data and technology stack on which teams can build and extend personalized interactions.

Evolve 19 | Kevin Campton & Sharat Radhakrishnan | Industry Focus | Autodesk ...

Evolve 19 | Gina Petruccelli | Let’s Dig Into Requirements

Evolve 19 | Dave Fox | Retaining Niche Talent in a Highly Competitive Environ...

Evolve 19 | Paul Legan | Going Beyond Metadata: Extracting Meaningful Informa...

The document discusses how digital asset management systems can extract meaningful information from digital assets through metadata and machine learning techniques. It describes how issues around organization, inconsistency, and limited use cases for assets can be addressed. Techniques for ingesting assets at scale including defining schemas, metadata profiles, and using smart tags are presented. The use of optical character recognition and Amazon Textract for extracting structured data from documents is highlighted. An example workflow for integrating these techniques into an AEM system is provided.

Evolve19 | Giancarlo Berner & Brett Butterfield | AI & Adobe Sensei

Evolve 19 | Gordon Pike | Prepping for Tomorrow - Creating a Flexible AEM Arc...

The document discusses creating flexible AEM architectures and implementing clean component-based architectures. It advocates starting with an architecture to guide development rather than delaying architecture. Progressive web apps are presented as having the broadest deployment footprint compared to other application types. The document also discusses using atomic design systems and component systems like React to achieve reuse.

Evolve 19 | Jayan Kandathil | Running AEM Workloads on Microsoft Azure

Evolve 19 | Amol Anand & Daniel Gordon | Author in AEM Once - Deliver Everywhere

This document discusses authoring content once and delivering it to multiple channels. It introduces experience fragments and content fragments in AEM that allow centrally editing reusable content and channel-specific content. It also discusses hybrid delivery that implements business logic once through Java models and renders multiple formats like HTML and JSON. The document provides examples of delivering content from AEM to different channels like websites, SPAs, mobile apps, emails, and voice/chat applications using APIs, editors, and integrations with other services.

Evolve 19 | Benjie Wheeler | Intro to Adobe Experience Manager 6.5

Evolve 19 | Bruce Swann | Adobe Campaign - Capabilities, Roadmap, and Fit wit...

The document discusses Adobe Campaign, its key capabilities for cross-channel marketing campaigns, and how it fits within the Adobe Experience Cloud. It outlines Adobe Campaign's capabilities for integrated customer profiles, targeted segmentation, cross-channel campaign orchestration, and integrated email. It also discusses Adobe Campaign's roadmap and strategy, including expanding into new channels, leveraging artificial intelligence, and integrating with the Adobe Experience Platform.

Evolve 19 | Pete Hoback & Francisco Fagalde | AEM QA, UAT, & Go Live