Using variations of a master content fragment lets you present different representations of the same content without duplicating it. For a summarized version, you keep the full article in the master content fragment and create a variation that contains only the summary. This keeps a single source of truth, so edits to the original article stay consistent while the summarized variant can be published where a brief version is needed. It also supports reuse across pages and contexts and makes localization and testing easier, since the variation is managed alongside the master. Modifying a component to show a shortened form would put the logic in the presentation layer and require separate handling in each place the article appears, which is harder to maintain. A variation of an experience fragment is more suited to assembling multiple assets for a layout, not necessarily to manage a source article’s summarized content. A workflow to generate a summary adds process overhead and isn’t as flexible for on-demand presentation across pages.

Leveraging a prebuilt, ready-to-use component is the fastest way to deliver when the goal is basic text editing with minimal effort. The Core Text Component in AEM 6.5 comes with built-in rich text editing (the standard editor) and integrates smoothly with the page authoring experience. This means you can drop it into a page and have a functional text block with the essential formatting options right away, without writing new code or extensive configuration. It also keeps styling consistent across pages with little to no custom work, which helps meet a tight deadline. Using HTML Source Edit would require authors to work with raw HTML, which is more error-prone and doesn’t align with a simple, quick-setup workflow. Creating a new Text Component would entail full development, testing, and maintenance, taking significantly more time. The Foundation Text Component is older and not as aligned with the current approach Focused on rapid delivery and consistency, the Core Text Component is the best fit here.

DefaultInjectionStrategy.OPTIONAL means injections are non-mandatory. In a Sling Models class with this default, the framework will attempt to inject values for each field, but if a value can’t be found, the model still gets instantiated. The missing injection is typically left as null (or handled as empty if you use an Optional type), so your code must account for possible absence. This provides flexibility when some data sources aren’t available or optional data is fine to proceed with. If you need a specific field to be required despite the class default, you can override at the field level with an explicit injection setting to enforce a value.

ResourceResolver lets you access resources stored in the Sling/AEM repository (the JCR hierarchy) in a consistent, service- or request-scoped way. To get a Resource for a specific path, you first obtain a ResourceResolver from the ResourceResolverFactory, typically using a service user (via a subservice) or from a request. Once you have the resolver, you can fetch the resource with the path you want. Example pattern: - Build the login params, usually using a service user: map.put(ResourceResolverFactory.SUBSERVICE, "myService"); - Get the resolver: ResourceResolver resolver = resourceResolverFactory.getResourceResolver(params); - Retrieve the resource: Resource resource = resolver.getResource("/content/your/path"); - Always close the resolver when done: resolver.close(); This approach is about accessing repository resources through the resolver, not about direct database access, UI rendering, or authentication handling.

In AEM, page content and media assets are stored in different parts of the repository to keep structure and media management separate. Page content lives under /content, which acts as the main container for site pages and their hierarchical structure. Media assets, such as images and videos, live under /content/dam (Digital Asset Manager), giving them dedicated asset-specific handling, metadata, renditions, and versioning. The /var area is used for system and runtime data, not for authoring content or assets. Placing assets under /content/assets or elsewhere breaks the standard DAM workflow and loses the built-in asset management features.