The photo essay was a form. It had a grammar. A sequence of images, usually between eight and twenty, selected and ordered to carry a narrative or make an argument that no single photograph could sustain alone. It appeared in Life, Look, Paris Match, and later in the serious newspaper supplement magazines that proliferated through the 1980s and 1990s. It required an editor who understood sequencing, a photographer who thought in arcs rather than moments, and a reader who would sit with it for ten or fifteen minutes.

On Photography was published in 1977 and has not been out of print since. That fact alone suggests Sontag was doing something more than journalism. She was building a framework, and frameworks built well outlast the specific occasions that prompted them. Fifty years on, the book reads as both essential and incomplete — which is a more interesting verdict than either pure endorsement or dismissal. What Sontag got right was the fundamental argument about photography’s relationship to reality.

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.

Paid memberships have become the dominant independent publishing business model. The newsletter-plus-paywall combination pioneered by platforms like Substack has proven that readers will pay directly for content they value, without advertising as the intermediary. Building that infrastructure yourself — rather than through a platform that takes a cut and mediates your reader relationships — is achievable for publishers willing to navigate the setup. This is a practical overview of the main approaches, what they require, and who they suit.

The phrase “owned audience” appears often in publishing strategy conversations without always being defined clearly. It refers to an audience relationship that you hold directly — one where you can reach your readers without paying a platform, depending on an algorithm, or risking an account action. Email is the canonical example. RSS is another. Your own website with returning visitors is a third. Contrast this with a social media following: technically large, functionally rented.

Contentful is one of the oldest and most established headless CMS platforms. Launched in 2013, it pioneered the API-first CMS model that the broader industry has since adopted. It is a mature, well-documented platform with a large ecosystem of integrations, a capable editorial interface, and a content delivery infrastructure built for scale. For publishing teams evaluating headless CMS options, Contentful warrants serious consideration — with a clear-eyed understanding of where it excels and where its costs and complexity create friction.

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.

Both Drupal and WordPress power large publishing operations. The New York Post, The Economist, and Condé Nast have used WordPress at enterprise scale. The Economist, Reuters, and major government and academic publishers have built on Drupal. Saying one is categorically superior gets the question wrong — they represent different engineering philosophies that create different strengths and different friction points. For a publishing organization evaluating both seriously, the decision turns on a handful of specific characteristics.

Email deliverability — whether your newsletter lands in the inbox or the spam folder — is determined by a combination of technical configuration, sending behavior, and list hygiene. Publishers who manage their own email infrastructure need to understand all three. Those on managed platforms (Beehiiv, Ghost, ConvertKit) benefit from the platform’s sender reputation, but some configuration and list hygiene practices remain their responsibility regardless. The Technical Foundation: SPF, DKIM, and DMARC These three DNS-based standards authenticate your email and tell receiving mail servers that messages from your domain are legitimate.

Drupal occupies a specific and durable niche in the publishing world. It is not the easiest CMS to get started with, and it is not trying to be. What it offers is a structured, extensible content management framework that scales to genuinely complex editorial operations — the kind where content types, taxonomies, workflows, and access control matter as much as the editing interface. Major news organizations, government publishers, universities, and enterprise media companies run on Drupal.