Automatic Responsive Images in Hugo: How the Built‑In Pipeline Works
Learn how Hugo’s extended edition automatically creates multiple image sizes and srcset markup from a single source file, removing the need for manual resizing.
Loading…
ReadMeFeed / Community knowledge
#static-site
Real questions. Useful conversations. Find the people who know your stack.
Using Hugo Pipes to Generate Responsive Images Without External Tools
Learn how Hugo’s built‑in image processing (Hugo Pipes) can resize, fingerprint, and create responsive srcset attributes without external tools, plus the trade‑offs to watch for.
Jekyll Incremental Regeneration Stale Output Diagnostic Guide
Jekyll edits not appearing in _site with incremental regeneration on. Diagnostic guide for stale pages, cache drift, and missing updates after renames or moves, with ordered checks and fixes.
Adding a Custom Taxonomy in Hugo to Group Content by Series
Learn how to add a custom taxonomy in Hugo—such as a 'series' grouping—by configuring the site, tagging content, and verifying the generated term pages.
Static Build vs. Dedicated Server for Low-Traffic Storybook Deployments
When managing a Storybook instance for a low-traffic internal project, the primary goal is to minimize monthly compute costs without sacrificing the core documentation experience. Two documented deployment paths exist: executing build-storybook to generate a static site for hosting on a CDN or object store, or maintaining a dedicated Node.js server to serve
How do I serve index.html in subfolders with S3/Cloudfront?
Got a bucket called www.foo.site . In that site there's a landing page, an about page and some pages in a few bar/* folders. Each bar/* has an index.html page: bar/a/index.html, bar/b/index.html etc. The landing page is running fine (meaning www.foo.site will load when I browse to it) but the /about/index.html page and /bar/index.html pages aren't getting se
`aws s3 cp` vs `aws s3 sync` behavior and cost
I have a static site that I am deploying to s3 and then using CloudFront to distribute to users. After I build the site, I want to push the new build to s3 . I found 2 approaches to do that. aws s3 cp --recursive ./public/ s3://bucket-name --cache-control 'public, max-age=300, s-maxage=31536000' aws s3 sync --delete ./public/ s3://bucket-name --cache-control
Static prerendering versus client‑side hydration for screen‑reader compatibility
The user‑facing workflow in Jamstack must deliver content that screen readers can interpret immediately while supporting interactive components that update after load. Static site generators render full HTML with ARIA attributes at build time, guaranteeing initial accessibility, but they cannot reflect runtime state changes. Client‑side frameworks hydrate th
jamstack
hugo