How Webhooks and On-Demand Revalidation Keep Headless CMS Sites Current

·3 views

Static and ISR-based websites cache content for speed, but this means CMS updates may not appear live immediately after publishing. NomaCMS addresses this by sending a webhook POST request to a developer-configured HTTPS endpoint whenever content events like publish or update occur. The receiving app then uses Next.js functions such as revalidateTag or revalidatePath to selectively clear only the affected cache, avoiding a costly full site rebuild. Developers configure the webhook via the NomaCMS dashboard or SDK, setting a secret for HMAC-SHA256 signature verification to secure the handler. This approach gives content editors near-instant publish-to-live behavior while preserving the performance benefits of CDN and framework-level caching.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to implement WCAG accessibility standards in modern Angular (v21+)

A developer has shared practical methods for applying Web Content Accessibility Guidelines (WCAG) in real-world Angular applications using version 21 and above. WCAG, developed by the W3C, defines how to make web content accessible to people with visual, auditory, physical, cognitive, and neurological disabilities through four core principles: Perceivable, Operable, Understandable, and Robust. The article highlights that accessibility is rarely taught practically in university or developer courses, despite being legally required in many countries and beneficial for SEO and code quality. Key implementation techniques covered include using Angular Signals to dynamically update ARIA labels in response to UI state changes, and manually adding keyboard focus support to custom components built with non-semantic HTML elements like divs. The author argues that writing accessible code leads to cleaner DOM structure and broader software reach, making it a worthwhile engineering investment beyond mere compliance.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Bloomy, YC S26 Startup, Seeks Founding Engineer

Bloomy, a startup backed by Y Combinator's S26 batch, is currently hiring for a founding engineer role. The job listing was posted on Hacker News, a popular platform for tech recruitment. Founding engineer positions typically involve working closely with early leadership to shape core product and infrastructure. No further details about the company's focus or compensation were publicly available in the listing.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Google Trends tokens are IP-locked, silently breaking scrapers behind rotating proxies

A developer building a Google Trends scraper on the Apify platform discovered that widget tokens issued during the initial API call are tied to the originating IP address. The scraper worked flawlessly on a local machine but failed in production, where proxy servers rotated IP addresses between sequential requests. Counterintuitively, residential proxies — considered higher quality — caused more failures than datacenter proxies because they rotated IPs more aggressively, invalidating tokens even for basic timeline data. The fix involved pinning all requests within a single scraping run to the same IP using a sticky proxy session ID. With this change, a two-term comparison completed in roughly 16 seconds and returned full timeline and related-query data reliably.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why Blocking Session Cookie Reuse Alone Won't Secure Your Application

Session cookies store unique identifiers that servers use to maintain authenticated user sessions, but they offer no built-in way to verify which device or user is presenting them. Restricting cookie reuse across devices addresses only a surface-level symptom, failing to stop both intentional sharing by users and theft by attackers who have already compromised a device. The deeper vulnerability stems from relying on single-factor authentication, where a stolen cookie alone grants full access with no secondary verification. Security experts recommend layered defenses including multi-factor authentication, device fingerprinting, and behavioral monitoring to tackle root causes. Organizations that focus solely on cookie reuse restrictions risk a false sense of security while leaving more fundamental authentication weaknesses unresolved.

0 comments Read more at DEV Community