# authoring Published articles for authoring. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Ebb, Meet Flow: Intrinsic Design in a Nutshell DevFeed: [Ebb, Meet Flow: Intrinsic Design in a Nutshell]() Original publisher: [Read original article]() Author: L. Jeffrey Zeldman Published: 2026-08-18T17:24:50Z Content type: opinion Language: en Sources: [Jeffrey Zeldman]() Topics: [Responsive Design](), [web design](), [Front end](), [web-standards]() Tags: [authoring](), [best-practices](), [css](), [design](), [essentials](), [responsive](), [responsive-design](), [responsive-web-design](), [rwd](), [standards](), [state-of-the-web](), [the-essentials](), [the-profession](), [type](), [typography](), [usability](), [user-experience](), [ux](), [w3c](), [web-design](), [web-design-history](), [web-standards](), [webdesign](), [webtype]() ### AI overview This article explains intrinsic or fluid responsive design: define type scales for small and large screens, then let the browser interpolate between them according to viewport width. It connects the approach to earlier ideas about designing for the web's natural ebb and flow and to the development of Responsive Web Design through improved web standards and browser support. ### Source excerpt In 2020, the gifted makers of websites at Clearleft shared methods to achieve fluid responsive design. "Utopian" web design was (and still is) their half-kidding name for this approach, which Apple's Jen Simmons, working indendently, called "intrinsic design." Instead of chasing an ever-changing number of fixed breakpoints, utopian or intrinsic design follows the web's intrinsic [...] The post Ebb, Meet Flow: Intrinsic Design in a Nutshell appeared first on Jeffrey Zeldman Presents. ## Advanced Patterns: Grok + Hermes for Complex Workflows DevFeed: [Advanced Patterns: Grok + Hermes for Complex Workflows]() Original publisher: [Read original article]() Author: hi@meedamian.com (Damian Mee) Published: 2026-05-18T00:00:00Z Content type: tutorial Language: en Sources: [Damian Mee | Blog | Portfolio | About]() Topics: [Automation](), [sessions](), [Tool](), [Raspberry Pi]() Tags: [advanced](), [authoring](), [context](), [delegation](), [long-running](), [memory](), [multi-agent](), [pi](), [productivity](), [skills](), [workflows]() ### AI overview This developer post presents advanced workflow patterns for using Grok inside Hermes Agent. It discusses planning and sub-agent delegation, generating reusable SKILL.md files, and combining context handling with Hermes' memory tool for long-running projects. The author says these patterns improved productivity on Raspberry Pi projects and personal automation. ### Source excerpt Disclaimer: This post was generated by Grok 4.3 running inside Hermes Agent. Advanced Grok + Hermes Workflows Once you have the basics down, here are some powerful patterns for using Grok inside Hermes Agent. Multi-Agent Delegation Grok excels at planning. Use it to orchestrate sub-agents: hermes delegate --goal "Refactor the auth module" --model grok-4.3 Skill Authoring with Grok Grok is fantastic at writing reusable skills. Ask it to generate SKILL. ## Authoring Custom Spin Templates DevFeed: [Authoring Custom Spin Templates]() Original publisher: [Read original article]() Author: Thorsten Hans Published: 2025-05-28T12:00:00Z Content type: tutorial Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Command-line interface](), [code productivity]() Tags: [authoring](), [boost-developer-productivity](), [cli](), [compliance](), [how-to](), [install](), [templates]() ### AI overview A tutorial on creating, distributing, and installing custom templates for Spin CLI, with stated goals of improving developer productivity and supporting regulatory compliance. ### Source excerpt Learn how to create, distribute and install custom templates for Spin CLI to boost developer productivity and meet regulatory compliance. ## The path to structured content with Markdown DevFeed: [The path to structured content with Markdown]() Original publisher: [Read original article]() Author: Niklas Begley Published: 2024-06-06T07:00:00Z Content type: tutorial Language: en Sources: [Doctave - Build beautiful developer portals with docs-as-code]() Topics: [Markdown](), [Parser](), [Parsing](), [XML](), [Documentation]() Tags: [authoring](), [blog](), [documentation](), [markdown](), [structure](), [structured](), [syntax](), [technical](), [technical-documentation]() ### AI overview The article argues that Markdown has an underlying structure that is often hidden from authors, making it more similar to XML-based structured authoring than commonly assumed. It demonstrates how Markdown is transformed into an abstract syntax tree and represented as a tree-shaped JSON structure. ### Source excerpt This post was inspired by the Pros and Cons of Using Markdown for Technical Documentation Panel Discussion with Ed Marsh, Eric Holscher, and Fabrizio Ferri-Benedetti. Around the ~40 minute mark the discussion moves onto how to maintain a consistent style with Markdown documentation, especially in larger teams. The panel agrees that currently there are no clear ways to enforce a specific document structure when using Markdown. Fabrizzio then on goes on to say (54:15): Some day, someone is going to figure out a way to seamlessly grow Markdown into something that can mature into structured content I've been thinking about this a lot, and my claim is that Markdown and XML (which is traditionally used for structured authoring) are more similar than you would initially expect, and that the dream of adding validations and structure to Markdown is perhaps not too far away. The structure behind Markdown There's a commonly held belief that Markdown is not structured. There is some truth to this, but I'd argue it's more the case that the structure is hidden. While with most XML-based authoring tools you are manipulating the structure directly (or through a WYSIWYG editor), with Markdown we are one level removed from the actual underlying structure. To demonstrate, let's take a look at a quick example at how Markdown is actually almost equivalent to XML, if you squint a little. Let's take this Markdown content. 1 2 3 4 5 # Hello, world This is a paragraph **with some bold text** and this is an image When this Markdown is processed into HTML, it goes through a number of transformations. The first thing that happens is that the Markdown is converted into an Abstract Syntax Tree. This means taking the raw text of the Markdown, and converting into something more structured that a program can manipulate. Each Markdown parser does this a little bit differently, but we can see this in action with, for example, the AST Explorer tool. Let's take Markdown above, and paste it ## Don't Develop Just for Yourself - A Developer's Checklist to Accessibility DevFeed: [Don't Develop Just for Yourself - A Developer's Checklist to Accessibility]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:24.089000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [keyboard](), [Usability](), [alt text](), [aria](), [ui]() Tags: [accessibility](), [alt-text](), [aria](), [authoring](), [automated](), [blog-post](), [developer](), [keyboard](), [testing](), [usability](), [web](), [website]() ### AI overview A beginner-oriented accessibility checklist for developers. It recommends manually testing keyboard navigation, focus visibility, and other website interactions after automated testing, while noting that the process does not guarantee full accessibility. ### Source excerpt We, as developers, tend to develop sites unconsciously for people like ourselves. If we don't actively pay attention, the sites are often accessible only for certain types of people: Sighted mouse-users, who have good fine motor skills and are good at using computers. It leads to moments where no one who navigates the web with only a keyboard (or keyboard simulating device) can access and interact with the site. It is a pretty big group of people! We have a responsibility to make sites that work for all of our users. In some cases, it is required by law, but it is not the only reason we should care. This blog post is aimed for those at the beginning of their accessibility journey. You might know some things, like "always provide an alt-text for an image," but are unsure what to write there. Or you don't have any idea how to know if your site is accessible at all. Following this blog post won't make your site 100% accessible! The goal of this post is to provide some information about some things to check manually after using some automated testing. Keyboard Navigation First of all, abandon your mouse for a second. Don't use it. Try to navigate through the website using only the keyboard. Try to complete every task user needs to be able to complete on the website. Can you do it? Can you see where you are at the moment? Is the focus indicator (yes, that thing many designers and developers like to remove) visible enough? If you can't use the whole website with only a keyboard, that is an accessibility and usability problem. However, one thing to note here is that keyboard interaction is not necessarily accomplished with just tab and enter, as it has been at some point. The general pattern goes, as WAI-ARIA Authoring Practices state: A primary keyboard navigation convention common across all platforms is that the tab and shift+tab keys move focus from one UI component to another while other keys, primarily the arrow keys, move focus inside of components that include mult ## Custom Matrix Block Peer Validation Rules DevFeed: [Custom Matrix Block Peer Validation Rules]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2021-05-24T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Website]() Tags: [authoring](), [better](), [blocks](), [builder](), [cms](), [content](), [craft](), [custom](), [errors](), [experience](), [insights](), [leverage](), [matrix](), [module](), [peer](), [rules](), [validation]() ### AI overview A tutorial on extending Craft CMS Matrix block content builders with custom peer validation rules. The example validates sundae blocks by limiting scoop and topping counts, requiring at least one scoop, and rejecting a specific flavor combination. ### Source excerpt Leverage a Craft CMS module to add custom peer validation rules to your content builder Matrix blocks for a better content authoring experience ## Using Craft CMS as a Headless CMS with the GraphQL API DevFeed: [Using Craft CMS as a Headless CMS with the GraphQL API]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-01-20T05:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [GraphQL](), [API](), [Front end](), [Self-hosted]() Tags: [added](), [api](), [authoring](), [cms](), [craft](), [formalized](), [frontend](), [gives](), [graphql](), [headless](), [here-s](), [insights](), [layer](), [practical](), [structured](), [website]() ### AI overview This tutorial explains how to use Craft CMS as a headless CMS through its GraphQL API. It discusses the API's structured data access, its use with separate frontends, and the distinction between Craft CMS's first-party implementation and the CraftQL plugin. ### Source excerpt Craft CMS 3.3 added a GraphQL layer that gives your website a formalized, structured API out of the box. Here's how to use GraphQL + Craft CMS as a "headless" CMS ## Creating a Content Builder in Craft CMS DevFeed: [Creating a Content Builder in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2017-01-16T18:59:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Matrix](), [Front end](), [User experience (UX)](), [Website]() Tags: [article](), [authoring](), [better](), [block](), [blocks](), [builder](), [client](), [cms](), [content](), [create](), [field](), [frontend](), [giving](), [insights](), [just](), [matrix](), [rich](), [text](), [using]() ### AI overview This tutorial explains how to use Craft CMS's Matrix Block to build a structured content builder for clients. It argues that constrained block-based authoring can provide a better experience than an unrestricted Rich Text field. ### Source excerpt Using the Matrix block to create a "content builder" for your client is much better than just giving them a Rich Text field