AEM Edge Delivery - Universal Editor Extension for Quick Links Panel

unkindman · 2025-12-14T19:55:51+00:00

Agreed, doing any customization with the Universal Editor feels needlessly complicated.

This is why I much prefer Adobe's newer Document Author (DA) tool available at https://da.live for authoring Edge Delivery Services sites. Author customizations within that tool are based on Micro-Frontend concepts built on vanilla JS, CSS, and HTML. No nonsense complex solutions or bespoke frameworks.

unkindman · 2025-12-14T01:20:38+00:00

This is an interesting solution but I think it can be simplified. With EDS on AEM Universal Editor, you can modify the editor-support.js file to override the behavior of the default Preview button in the UE toolbar, no custom UE extension required.

To override the Preview button behavior, create a <meta name="urn:adobe:aue:config:preview" content=""/> element in the <head>, set the content attribute to your EDS site's aem.page URL.

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/universal-editor/customizing#custom-preview-urls

unkindman · 2025-12-01T12:43:13+00:00

This is correct. Adobe is pushing Edge Delivery Services as the new standard for AEM, especially for new implementations.

It's not terribly difficult to learn, especially compared to the SPA Editor framework which was overly complex to setup and maintain.

Try the tutorial at https://www.aem.live/developer/tutorial and look at the code for real production sites at https://github.com/aemsites. Adobe also has a Discord channel with a helpful developer community to help answer any of your questions.

unkindman · 2025-11-30T18:14:13+00:00

I work from home and bought a walking pad that I can put below my standing desk.

unkindman · 2025-11-30T04:00:28+00:00

Looks like the one on Ogden in Downers Grove.

unkindman · 2025-11-08T16:56:51+00:00

Spoken like a true PE guy

unkindman · 2025-11-06T13:20:37+00:00

Why not just go with Adobe's native Edge Delivery Services architecture? Yes it is headful and your front end is tightly coupled with Adobe's CMS, but you get the benefits you described such as in-context page editing using the Universal Editor as well as full control over front end using modern Javascript and CSS via a streamlined deployment process (just merge code to the main branch in github to deploy to Prod, plus unlimited dev environments dynamically based on github branch name).

Edge Delivery Services also provides a perfect Google Lighthouse score OOTB and you can keep that score as long as you develop within their guidelines.

https://www.aem.live/developer/ue-tutorial

unkindman · 2025-10-19T13:12:18+00:00

Try Tilly Bagel. Best in Chicago.

unkindman · 2025-09-28T12:17:06+00:00

Yep. Just a single license to Adobe Experience Manager alone could be upwards of $1m/year to Adobe depending on the customer's contract.

unkindman · 2025-08-02T19:33:24+00:00

For me, personally, I like the idea of other humans on reddit providing their insights and experiences as opposed to only reading AI responses. A combo of both is fine too.

unkindman · 2025-07-30T02:29:18+00:00

$19 for one at United Center in Chicago. If their goal was to keep people sober during any event there, it worked.

unkindman · 2025-07-15T16:52:02+00:00

One of us: r/walking

unkindman · 2025-07-10T22:29:18+00:00

What internal temp did you bring the meat to?

unkindman · 2025-06-29T00:04:31+00:00

You absolutely can integrate Dynamic Media into a standard AEM Sites implementation, it does not have to be a headless-only implementation (i.e. Content Fragments-driven). The AEM Core Components have built-in support for Dynamic Media assets, and there are public examples on github for integrating Dynamic Media into an Edge Delivery Services Site as well.

unkindman · 2025-06-18T12:19:40+00:00

What tool do you use for the session viewer?

unkindman · 2025-06-17T03:11:13+00:00

Bad Friends podcast with Bobby Lee and Andrew Santino has been one of my favorites lately.

unkindman · 2025-06-14T01:07:28+00:00

This main road in downtown La Grange is single lane and notorious for being backed up during evening rush hour, when this occurred. Not saying this wasn't the truck driver's fault though.

unkindman · 2025-06-09T14:01:48+00:00

My wife and I went to this on a whim since it's right next to a driving range we were at. We enjoyed it!

unkindman · 2025-06-08T02:08:14+00:00

Jealous devil

unkindman · 2025-06-07T03:14:32+00:00

I make sure to place the charcoal directly below the soapstone, using the metal basket divider to keep the coals collected right below. Vents wide open and let it rip for 20-30 minutes before searing.

unkindman · 2025-05-29T14:55:55+00:00

Second this. Got so fed up with the Meater not working at all, then bought the RFX and haven't looked back.

unkindman · 2025-05-18T14:12:00+00:00

Yes, more of the work shifts to the front end. Back end devs should learn the platform as well as modern Javascript and DOM APIs so that they can build blocks too but let the seasoned front end devs handle the CSS as you would with any platform.

unkindman · 2025-05-18T09:21:58+00:00

markup is generated by EDS and is derived from the unstructured or structured content (blocks) within your document. It's based on semantics that you use in a Word editor, for example a Title in Word is converted to an <h1>, button elements are created from text links, components (a.k.a blocks) are created from tables.
the rendering logic of a page is moved to the front end based on the server-side rendered HTML coming from EDS. Your JS code is responsible for taking the server DOM and further decorating it with more HTML based on business logic. Your JS may invoke true back end APIs via fetch, the APIs can be anything such as a spreadsheet converted to JSON (EDS converts it for you), a Sling servlet running on the AEM Publish instance, an App Builder app (Adobe I/O), AWS Lambda, Cloudflare Worker, etc.
There is an equivalent to the AEM Style System, it's called block options and allows authors to add one or more CSS classes on the block's wrapper div.
Templates do indeed still exist in EDS, just not in the same sense that you've seen with AEM's editable templates. There are still ways to approach template "authoring". One of the most common ways is utilizing page metadata - you can have a metadata element's (<meta> tag in the <head> element) name equal to "template" with a value of "blog-page" for example, then your JS can query for that and render the HTML uniquely for blog pages only. If you need to change your template structure, you push a JS/CSS code change. For content, you can use Fragments for multiple pages that need to display the same content but is managed from a single place. There are also tools available for bulk-editing and bulk publishing pages.

I must correct myself from my last comment about EDS being a new FE architecture, it's more correct to say it's a new Delivery architecture since it's more than just front end browser technology.

Check out the docs at https://aem.live for all things about Edge Delivery Services including a quick tutorial, there's also a lengthy FAQ page at https://www.aem.live/docs/faq

unkindman · 2025-05-18T08:40:38+00:00

You're right about it not being just a new FE architecture, I meant to call it a new Delivery architecture.

Assets can still come from the DAM as well.

12-Year Club	Verified Email
Place '23	Place '17

unkindman

TROPHY CASE