Developer builds self-publishing static Nuxt blog with scheduled posts and auto-rebuilds

·2 views

A freelance developer has built a custom publishing engine on top of a fully static Nuxt 4 (SSG) site to enable scheduled article releases without a traditional server. The system uses Storyblok as a headless CMS, a Nitro server running under PM2, and GitHub Actions to handle deploys. A Nitro scheduled task checks every hour for due articles, pushes approved drafts to the CMS in Storyblok's richtext format, and triggers a single site rebuild via GitHub's workflow_dispatch API. Drafts are stored server-side with statuses and publish dates, ensuring nothing reaches the live site until its scheduled moment. The setup requires no external queue service or dedicated cron infrastructure, relying entirely on tools already present in the Nuxt stack.

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)

What Makes Someone an Engineer? One Tech Worker's Search for Identity

A technology worker at a school reflects on whether their problem-solving mindset and curiosity qualify them as an engineer, despite lacking a formal engineering title or degree. The question was sparked after they discovered their name listed under an 'Engineering Team' at a previous employer, where their official role was a network installation and computer technician apprentice. Working in a school environment, they describe frustration with outdated procedures and a personal drive to improve systems and help colleagues, including independently learning to operate an industrial laminator outside their job description. The author notes a tension between self-identification and formal credentials, pointing out that engineering titles carry strict legal weight in Canada but are applied loosely in the United States. Ultimately, they question whether the engineer title holds genuine meaning, and whether a philosophical, questioning mindset is itself the defining trait of an engineer.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Agents Match Humans Closely in Protein Binder Design Trial, Wet Lab Shows

At a February 2026 one-day hackathon organized by muni, six autonomous AI agents including Claude Sonnet 4.6 designed protein binders targeting TREM2, a receptor relevant to neurological research. Adaptyv Bio tested 35 agent-designed binders in a wet lab, finding that 12 successfully bound TREM2, yielding a 34.3% hit rate. Human designers performed slightly better, achieving a 38.5% hit rate with 25 out of 65 binders binding successfully, though the gap was narrow. The campaign also produced high-affinity binders on both sides, with the strongest result coming from a human submission at 1.11 nM KD versus 3.64 nM KD for the top AI-designed binder. Experts caution that the aggregate AI result should not be attributed to any single model and that the findings reflect progress in AI-assisted biotech tooling rather than a proven shortcut to drug discovery.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Engineer Builds Publishing Platform to Preserve and Share Technical Knowledge

A software engineer began writing regularly to prevent valuable engineering knowledge — from architecture decisions to incident lessons — from being lost over time. Publishing across multiple platforms like Medium, Hashnode, and DEV.to proved time-consuming, as each article required repeated formatting, tagging, and metadata work after writing. This led the engineer to design an automation tool that treats articles as immutable releases deployed through a pipeline to multiple publishing destinations via platform-specific connectors. During the design process, the engineer realized the harder problem was not publishing but the thinking and reflection that precedes writing. The project evolved into a broader platform aimed at supporting the entire process of developing and sharing technical ideas, not just distributing finished content.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds one Vue app that runs on desktop, Android, and web simultaneously

A developer created a single Vue.js Reddit client that runs as a desktop app via Tauri (Rust), an Android app via Capacitor, and a standard web app — all from one codebase. The project uses one shared UI, a unified Reddit API integration, and a single OAuth flow targeting three platforms. Key challenges included platform-specific build requirements, since Tauri relies on each OS's native toolchain, meaning cross-platform releases require a CI pipeline with separate runners per operating system. OAuth handling also proved complex in packaged apps, as there is no web server to receive redirects, requiring custom deep-link schemes on both desktop and Android. The developer notes that while the approach is viable for web developers targeting multiple platforms, real-world packaging and authentication details demand significantly more effort than typical tutorials suggest.

0 comments Read more at DEV Community