For language and meaning nerds, the actual ~things~ that live outside the vocabulary and syntax of a sentence but carry important meaning — like emphasis or rhythm — are called "suprasegmentals". In linguistics, "Prosody" is the study of suprasegmentals, and it rocks.
This matters a lot in digital content, because the push to make content more flexible and less brittle often means "removing decoration so it can be handled somewhere else." When done naively, though, that can strip away the "suprasegmentals" and discard real meaning.
It's like copying a bunch of formatted text and pasting it into "plain text" — a lot of what vanishes might be purely aesthetic decoration, but things like italicization for emphasis get lost as well, and that conveys actual meaning.
As with text, the answer is to capture the underlying intent, even if the decision about how that meaning is is conveyed (typeface? position? coloration? something else?) gets defered or is left up to another system entirely. That's why HTML moved from the <i> tag to <em>.
And it's why in complex content systems, things like "layout" and "styling" can't be ignored entirely — when used effectively they communicate information, not just aesthetic decoration. Capture the suprasegmentals explicitly, then let the designers interpret them!
• • •
Missing some Tweet in this thread? You can try to
force a refresh
So, as @danieleharper mentioned, @kristinrawls and I Kool-Aid-Man'd into an episode of @idsgpod to chat about the overlap between Christian fundamentalism and the alt-right…
There are numerous fascinating (and deeply troubling) connections — we focused on the direct and explicit ones embodied by Doug Wilson's "paleoconfederate" flavor of Christian Reconstructionism, the stuff @kristinrawls has been diving into for @CRightcast.
But we also touched on the less explicit thematic and conceptual building blocks that the alt-right movement shares with broader fundamentalism in the Christian Right. The idealization of a "pure and unsullied" past; rigid gender roles and masculine authority/female submission…
There are three basic ways to approach content modeling, and I'd argue that each of them have _strengths_ but no single one is philosophically correct or incorrect. Each is just a place to start.
The approach you hear about when a content architect describes ~the process~ is what I think of as "platonic content." You start with a communication or publishing concept and iron out your content types, their properties, etc. in a way that best describes their essential nature.
"We want to do interviews. What _is_ an interview, conceptually? Well, we'll need a subject, perhaps multiple subjects…" and so on.
So, last week @beep and I had a fascinating conversation with @petermcreaper and @mkeftz about the work they're doing on @interplayapp; among other things we circled around the ideas Peter mentioned in his post about design artifacts… it's worth a read. pete.studio/notes/design-f…
@petermcreaper's thesis in that post is pretty straightforward: the intermediary design files accumulated in the process of developing a site — particularly one that's heavily component and pattern based — are disposable, temporary artifacts and not the "source of truth."
It's a thing @gregddunlap and I talked about over the years WRT content models — it's fascinating to (again!) see similarities popping up. With content, you accumulate an endless pile of spreadsheets and similar docs to iron out types, properties, relationships, and so on.
Here to say once again that Screaming Frog SEO is an amazing nuclear-powered chainsaw of a tool for web work.
Its out of box config is geared towards SEO optimization (naturally, given the name) — making sure all your pages have decent metadata, stuff like that. But learning how it does what it does and configuring it to your needs turns it into something much, much more.
Most CMSs leave some default CSS classes or IDs in their markup to indicate template or content types used when rendering a page — Screaming Frog lets you run custom regexes during its crawl to extract those, generating a pre-categorized list of what content type each page is.
The concerns that nag me about the booming universe of Design Tokens are all issues @davereid and I encountered when we built and supported the Token system for Drupal. I'm still trying to suss out how much of that is "learning from experience" vs "applying the wrong lessons."
The token system for Drupal was originally conceived around '07 or so. Its ecosystem was evolving to give site builders composable pieces ("image-displayer" and "grid-display" and "pager") rather than drop-in functionality ("forum", "gallery", etc).
Around then we built one of the first large-scale production sites that used Drupal's early "click-together tools" instead of pure code: Sony/BMG Music's artist site platform, which allowed them to spin up new interactive community sites for each artist in just a couple of days.
While breaking down the different conceptual building blocks of modern evangelical "Purity Culture" for the next episode of @CRightcast I've come across a critical component that — weirdly enough — also appears a lot in the internet Rationalist community.
A big part of tackling complicated issues — poverty, why evil exists, why my wifi keeps dropping — is getting to root causes and patterns, rather than just focusing on the surface stuff. It's important!
Often, the process of searching for those underlying patterns can help us sort through the confusion and identify how a challenging problem can be solved.
…But that "what's REALLY going on here?" process can also be used to obfuscate, to minimize, to shift blame.