AEM Franklin / Helix / Composability: Pros and Cons | AEM Community Blog Seeding

[#1]

AEM Franklin / Helix / Composability: Pros and Cons by Krassimir Boyanov

Abstract

What is AEM Franklin?
AEM Franklin, also known as Project Helix or Composability, is a new way to publish AEM pages using Google Drive or Microsoft Office via Sharepoint. Instead of components, Franklin uses “blocks” to build pages. Blocks are pieces of a document that will be transformed into web page content. There are boilerplate blocks that define commonly used page components such as: text, images, buttons, headers, footers, hero images, etc. These blocks allow users to generate new pages quickly and even create templates to reuse.

AEM Franklin projects will be managed using the Helix Bot and the Sidekick, a Github app that publishes the content generated by authors. These pages can live alongside standard AEM pages, so users can use whichever tool is most appropriate for their current needs.

What are the Pros?
The main selling point for AEM Franklin is that users will be using software they are already familiar with, like Microsoft Office products Word and Excel, or Google Drive applications Pages and Sheets. If users wish to create new templates and page designs, there is no additional specialized knowledge required like HTML, CSS, and JavaScript. It is easy to publish this new content directly.

An additional benefit to AEM Franklin is that pages are extremely fast and well optimized with a Lighthouse score of 99 or 100. This can help when creating an initial product with a short delivery window. On the other hand, it’s possible to achieve these scores with a standard AEM page, even if it requires more forethought and implementing programming best practices.

Read Full Blog

AEM Franklin / Helix / Composability: Pros and Cons

Q&A

Please use this thread to ask the related questions.