Nuxt.js: Empowering Developers
npx create-nuxt-app app-name
After creating Nuxt.js, the core team realized two things: many of them were writing the same boilerplate foundations for every application; what emerged as best practices in the Jamstack community didn’t have to be manually replicated every time. Instead, modern software should do one of the many things it does best — empower productivity by automating tedium; thus, they made create-nuxt-app.
With create-nuxt-app, developers can select their desired targets and technologies with the stroke of a key. The best part? create-nuxt-app ties everything together for you (batteries included). Static site generation for peerless performance through Content Delivery Network (CDN) edge server deployment? That’s an option. GitHub Actions for easily-automated Continuous Integration (CI) / Continuous Delivery (CD) processes? You bet. The Nuxt Content module for a Git-based, headless content management system (CMS) contributors love? Yup, that’s one, too. For the Nexus Cognitive site, we chose all three options to supercharge our development and content workflows.
Netlify CMS: Empowering Authors
At first blush, Nuxt Content and Netlify CMS appear to be vying for the same layer of your Jamstack. Both are Git-based. Both are headless content management sytems. The crucial difference between the two technologies is in content authoring: with Nuxt Content, developers must use editors like Visual Studio Code or rely on development servers; with Netlify CMS, authors may use an intuitive, web-based interface from anywhere.
Writing code and writing content also share similarities in collaborative workflows. Developers write code, submit it for review, make revisions, then stage it for publication. Similarly, authors write content, submit it for review, make revisions, then schedule it for publication. Not surprisingly, enabling a familiar Editorial Workflow in Netlify CMS requires one line in a configuration file:
The creators of Netlify CMS kept simplicity in mind, and they understand the overlaps between writing code and writing content offer benefits. On the surface, authors can manage the content lifecycle through an easy, drag-and-drop interface. Under the hood, Git manages the content lifecycle through lightweight branches. And, controlling content through Git enables offline work through repository distribution and content safety through historic versioning.
Ultimately, because Nuxt Content and Netlify CMS leverage the same technologies while enabling diverse workflows, they are entirely well-suited for one another; in truth, they are allies (not adversaries). Because Nuxt.js statically generates web applications and Netlify CMS manages their contents in Git, though, creating content isn’t the end of the story.
GitHub: Empowering Teams
Managing application code in Git makes developer collaboration a breeze. Writing content in Netlify CMS makes author collaboration seamless. What about linting, testing, building, and deploying updates to web applications?
Thankfully, when teams share remote repositories on GitHub, GitHub Actions make it possible to automate all those software workflows. With webhooks, GitHub Actions trigger CI / CD processes on Git actions: when developers create Pull Requests, immediately lint and test their updates; when developers merge branches, build and deploy those updates.
These automated processes are critical to Git-based content authoring: with them, non-developers don’t need to know anything about software lifecycles. When authors publish their works through Netlify CMS, their updates undergo the same automated processes as any others. And, with automated CI / CD processes, Jamstack application teams develop new features instead of managing build processes.
Taken together, Nuxt.js, Netlify CMS, and GitHub make Jamstack web development, content authoring, and application deployment easy because static site generation, distributed content workflows, and automated CI / CD processes make collaboration simple. Do you want to leverage the simplicity and efficiency of the Jamstack to power your future successes? Contact us.