Choosing an htmx swap strategy for list and form updates
Learn how to pick the right htmx swap mode—innerHTML, outerHTML, afterbegin, beforeend, delete, or none—for updating lists or forms without a full page reload.
Loading…
ReadMeFeed / Community knowledge
#frontend
Real questions. Useful conversations. Find the people who know your stack.
htmxAlpine.js List Rendering: Why Keyed Templates Matter for State Persistence
Alpine.js renders lists with x-for on <template> tags. Using a stable :key preserves DOM node identity—focus, transitions, input values—when arrays reorder. A worked example shows why index keys break and how to choose Alpine over a SPA for server-rendered pages with interactive pockets.
alpinejsHow Behance Delivers High‑Resolution Portfolios Without Killing Page Load
Behance separates lightweight metadata from heavy image files, uses lazy‑loading and CDN‑edge format switching to keep portfolios fast and high‑fidelity.
Vite Environment Variables: Designing a Safe Client‑Side Config
Learn how to safely expose only non‑secret configuration to the browser using Vite’s VITE_-prefixed environment variables, understand the trust boundary, and verify that no secrets leak into the built bundle.
viteRemix Server Actions: One‑File Data Mutation
Remix Server Actions let you mutate data directly from the client without exposing a separate API. This blog walks through a concrete example, highlights trade‑offs, and gives a step‑by‑step checklist for safe implementation.
remixSvelte Reactive Statements: Stop Manually Syncing Derived Values
Svelte's $: reactive statements turn derived state from an update-everywhere liability into a declare-once guarantee. Here's how they work, a working counter example, and the performance trade-off to watch.
Using Tailwind CSS Arbitrary Values for One‑Off Styling
Learn how Tailwind CSS arbitrary values let you inject any CSS utility directly in markup, see a responsive card example, and understand the trade‑offs of bypassing the design system.
tailwindcssUsing Stylus Transparent Mixins to Simplify Vendor Prefixes
Learn how Stylus transparent mixins let you write vendor‑prefix‑heavy CSS as a simple property, reducing boilerplate while keeping full language power.
stylusMaterializeCSS v1.x and the jQuery Dependency: An Architecture Note
MaterializeCSS 1.x ties its interactive components to jQuery 2.x/3.x, inflating bundles and widening attack surfaces. This guide explains the requirements, minimal design options, trust boundaries, operational checks, failure modes, and when to rethink the architecture.
materializecss