Home

sling-patterns a pattern library for Sling (AEM)

Goal

Provide a pattern library similar http://corej2eepatterns.com/ and the famous GoF Design Patterns.

#About patterns Patterns are a structured way to document solutions for recurring problems. The main benefit of patterns, is that they help recognize known and solved problems and the matching solution. The names defined for each pattern simplify communication.

#Structure to document a pattern Each pattern will contain the following properties and chapters.

• Name
• Problem
• Solution
• Consequences
• Related Patterns

#Proposed patterns ##Content Suffix Use the path to determine the rendering context and the suffix for the content path. ##Static Page Type Use a specific page type as trigger for custom functionality, not using any CMS functionality within this page. ##View Only Trivial use cases should only contain a resourceType, dialog and view

#Implementation driven The following pattern names, directly match an existing interface/solution in Sling. Nevertheless it might make sense to document them in pattern language, to clarify when those solutions apply best. ##Rewriter https://sling.apache.org/documentation/bundles/output-rewriting-pipelines-org-apache-sling-rewriter.html ##Filter https://sling.apache.org/documentation/the-sling-engine/filters.html ##Adaptable http://sling.apache.org/documentation/the-sling-engine/adapters.html