Controlling Netlify Deploy Triggers Without Breaking Your Branch Workflow
Connect a repo to Netlify and every push can trigger a build. Learn how to separate production deploys from preview builds using branch rules and netlify.toml.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Connect a repo to Netlify and every push can trigger a build. Learn how to separate production deploys from preview builds using branch rules and netlify.toml.
Hugo Modules replace Git submodules with Go-module semantics for versioned, composable theme dependencies. This post walks through migration, mount ordering, asset pipelines, and the trade-offs you'll hit in practice.
Compare Jekyll's built-in paginate with jekyll-paginate-v2 for 500+ posts. Core only paginates the main index; v2 adds category/tag/collection pagination, trail links, and JSON output but multiplies output files ~5× and needs GitHub Actions. Includes config, layout, and verification steps.
Static sites often need backend logic, but managing servers adds overhead. Netlify Functions provide a serverless middle ground-deploy from your repo, proxy APIs, and stay within static workflow constraints.
Use gatsby-plugin-image to generate WebP, AVIF, and responsive srcSets at build time instead of shipping heavy unoptimized images.
Static Gatsby sites often ship bulky images that hurt performance. This post shows how gatsby‑plugin‑image solves that, with a hands‑on example, trade‑offs, and a quick start.
Jekyll Collections let you model structured content—like releases or products—with custom folders and permalinks. Learn how to configure them, implement pagination with jekyll-paginate-v2, and choose between Collections and Data Files.
Combine Astro content collections with a Zod schema and the paginate() helper to get type-checked frontmatter, draft filtering, and fully static /blog/N pages at build time.
Dreamweaver's .dwt template system enforces layout consistency at author time and strips its logic on save — useful for FTP-deployed sites that can't run a build pipeline. Covers editable, optional, repeating regions, nested templates, and hard limits that make migration painful.