124Compare

Two options side by side — Flow vs Apex, profiles vs permission sets. The shape a technical post reaches for constantly and has to hand-build every time.

Use it for

Two legitimate choices with different trade-offs
--verdict when you ARE recommending one

Not for

Do and don't — colouring one green and one red makes an editorial judgement the content may not be making. That is why this is neutral by default
Three or more options — use a Table

Neutral

Flow

No deployment for small changes
Admins can maintain it
Harder to unit test

Apex

Real tests and version control
Handles bulk cleanly
Needs a developer

markup

<div class="ns-compare">
  <div class="ns-compare__side"><p class="ns-compare__title">Flow</p><ul><li>No deployment for small changes</li><li>Admins can maintain it</li><li>Harder to unit test</li></ul></div>
  <div class="ns-compare__side"><p class="ns-compare__title">Apex</p><ul><li>Real tests and version control</li><li>Handles bulk cleanly</li><li>Needs a developer</li></ul></div>
</div>

With a verdict

Workflow rules

Retired for new automation

Record-triggered flow

The supported path
Before-save updates are fast

markup

<div class="ns-compare">
  <div class="ns-compare__side"><p class="ns-compare__title">Workflow rules</p><ul><li>Retired for new automation</li></ul></div>
  <div class="ns-compare__side ns-compare__side--verdict"><p class="ns-compare__title">Record-triggered flow</p><ul><li>The supported path</li><li>Before-save updates are fast</li></ul></div>
</div>

Accessibility contract

Each side has a real heading, so the comparison is navigable by heading rather than by reading order
--verdict marks the recommendation with the same 2px brand edge used for every current-item in the system