WordPress’s built-in content structure — title, body, categories, tags, featured image — covers the basics for most publishing use cases. When a publication needs richer, more structured content models — author bios with headshots and social links, event listings with dates and venues, product reviews with rating fields, press releases with distribution metadata — the standard fields run out quickly. Advanced Custom Fields (ACF) is the plugin that WordPress publishers reach for to extend that content model.

Cloudflare Pages is one of the best hosting targets for Hugo sites. It is fast, globally distributed, free for most publishing workloads, and integrates cleanly with GitHub repositories. You can deploy directly through Cloudflare’s built-in Git integration — or through a GitHub Actions workflow for more control over the build process. This guide covers both approaches and when to choose each. Option 1: Cloudflare’s Direct Git Integration The simplest path requires no GitHub Actions configuration.

Eleventy (11ty) is a JavaScript-based static site generator that has grown into one of the most flexible options in its category. Where Hugo makes strong structural decisions and asks you to work within them, Eleventy makes almost none — it is a set of tools for turning content into HTML, with minimal opinions about how your project should be organized. That flexibility is genuinely powerful and genuinely requires more upfront decision-making.

Taxonomies are Hugo’s system for classifying and grouping content. Used well, they provide the structural backbone of a publishing site — the navigation paths, archive pages, and content relationships that let readers move through a site meaningfully. Hugo’s taxonomy system is flexible and powerful, but it requires deliberate configuration to use effectively. What Hugo’s Taxonomy System Does A taxonomy is a classification dimension. Tags and categories are the two built into Hugo by default, but you can define any number of custom taxonomies — series, authors, topics, formats, locations — and Hugo will generate archive pages and RSS feeds for each.

Hugo archetypes are content templates that pre-populate frontmatter when you create new content with hugo new. They are a small feature with a disproportionate practical impact on a publication’s day-to-day workflow: every new post or page starts with the correct structure, required fields are present, and authors do not need to remember the exact frontmatter format. The Default Archetype Hugo ships with a single default archetype at archetypes/default.md: --- title: "{{ replace .

Hugo has a built-in image processing pipeline that handles resizing, format conversion, and optimization at build time — no external service, no plugin, no JavaScript-based lazy loading required. For publishing sites where images are a significant part of content, understanding Hugo’s image processing is worth the investment. The result is faster pages with properly sized images served in modern formats, generated automatically from source files. Page Resources vs Global Resources Hugo works with images in two contexts:

Hugo partials are reusable template fragments — the building blocks of a maintainable Hugo theme. Any piece of HTML that appears in more than one place belongs in a partial: site headers, footers, navigation menus, article cards, SEO meta tags, social sharing blocks, author bios. Once defined, a partial is called with a single line from any template. This guide covers the full range of how partials work and patterns that make them practical for a publishing site.

Hugo Pipes is Hugo’s built-in asset processing pipeline. It handles Sass/SCSS compilation, CSS and JavaScript minification, fingerprinting for cache busting, and bundling — at build time, without external build tools like Webpack or Vite. For publishers running Hugo sites, understanding Pipes is the difference between manually managing compiled CSS and having the build handle it automatically. The Assets Directory Hugo Pipes works with files in the assets/ directory. Unlike static/, which copies files verbatim to the output, assets/ is a processing source — files there are available to Pipes functions but are only written to the output if explicitly processed and referenced.

Hugo shortcodes are reusable template fragments that can be embedded in Markdown content. They bridge the gap between Markdown’s intentional simplicity and the richer, more structured HTML that publishing sites often need — figure captions, callout boxes, video embeds, custom alert blocks, styled pull quotes — without requiring authors to write raw HTML in their content files. Hugo ships with a small set of built-in shortcodes and provides a straightforward system for building your own.

Migrating a WordPress site to Hugo is one of the most common transitions in publishing infrastructure. The reasons vary — performance, hosting cost, maintenance overhead, security exposure — but the path through the migration is broadly the same regardless of why you are making the move. This is a practical walkthrough of what the process actually involves. What You Are Gaining and What You Are Giving Up Before starting, be clear about the tradeoffs.

Listmonk is an open-source newsletter and mailing list manager — a self-hosted alternative to Mailchimp, ConvertKit, and similar services. It is written in Go, runs as a single binary backed by a PostgreSQL database, and handles subscriber management, campaign creation, list segmentation, and send scheduling. For publishers committed to owning their infrastructure, Listmonk is the most capable self-hosted option in the category. What Listmonk Provides Listmonk handles the management and orchestration layer of email newsletters: subscriber lists, subscriber data, campaign drafting, template management, tracking, and scheduling.

Hugo is fast to build and fast to get started with, but a blank new site has some deliberate setup work before it is ready to publish. This walkthrough covers the full process from installation through your first deployed post. Installing Hugo Hugo distributes as a single binary — no runtime dependencies, no package manager required after the initial install. macOS: brew install hugo Linux (Debian/Ubuntu): sudo apt install hugo Or download the latest binary directly from the Hugo releases page and add it to your PATH.

The WordPress block editor — introduced in 2018 as the Gutenberg project and now simply the default editing experience — has matured into a genuinely capable publishing tool. It was controversial at launch and the criticism was fair: it was slow, unstable, and a poor replacement for the Classic Editor many publishers had built workflows around. Several years and dozens of releases later, it is a different product. For publishers either still avoiding it or using it without fully understanding its capabilities, this is a practical walkthrough of what it can actually do.

The WordPress REST API has been part of WordPress core since version 4.7. It transforms WordPress from a self-contained CMS into a content platform that can serve data to any application that can make an HTTP request — mobile apps, static front ends, third-party services, or another WordPress site. For publishers evaluating headless architecture or building integrations, understanding what the API provides (and how to use it) is increasingly essential.

Hugo is fast and file-based, but its editing experience is entirely command-line: you write Markdown in a text editor, commit to Git, and push to trigger a build. For solo developers this is fine. For publications with non-technical contributors, it is a significant barrier. Decap CMS (formerly Netlify CMS) solves this by adding a browser-based editorial interface to Hugo without abandoning the static site architecture. What Decap CMS Is Decap CMS is an open-source, Git-backed content management interface.

WordPress is the most attacked CMS on the internet not because it is inherently insecure but because it is the most common. Its market share makes it the highest-return target for automated scanning and exploitation. A default WordPress installation is not a hardened one — but hardening it is straightforward, well-documented work that most publishers skip until something goes wrong. This checklist covers the high-impact measures that materially reduce your attack surface.