brutalism
177 Huntington
Guidelines for Brutalist Web Design
An Article by David Bryant Copeland- Content is readable on all reasonable screens and devices.
- Only hyperlinks and buttons respond to clicks.
- Hyperlinks are underlined and buttons look like buttons.
- The back button works as expected.
- View content by scrolling.
- Decoration when needed and no unrelated content.
- Performance is a feature.
This page is a truly naked, brutalist html quine
An Article by Leon BambrickI decided to make a truly naked, brutalist html page, that is itself a quine. And this page is it.
Viewing the source of this page should reveal a page identical to the page you are now seeing. Nothing is hidden. It's a true "What you see is what you get."
What On Earth is a Brutalist Website?
An ArticleSome of the web’s early richness has gradually been getting lost in a sea of landing pages, hero images, sans-serifs, and calls-to-action. “Web brutalism” is a valid reminder that there is still a world of possibilities out there, if we are bold enough to break free of our UI kits and stock photos.
Web Brutalism, seamfulness, and notion
An Essay by Brandon DornHow a tool for sensemaking reconciles two distinct software design ideologies.
- Seamful vs. seamless
- Reveling in infrastructure
- The brilliance of notion
- How our understanding is working
The split personality of brutalist web development
An ArticleWhen brutalist web design isn’t going all in on rationalism and functionality, it’s laughing in the face of rationalism and functionality. All clear?
The term has grown to encompass approaches that are in many senses at odds with each other. Indeed, Pascal Deville, who founded the Brutalist Websites directory after coining the term in 2014, thinks the style has splintered into three micro-stylistics:
- Purists,
- UX minimalists,
- Anti-ists (or artists).
How to Think About Notes
Thinking in terms of outputs
In our use of digital and analogue filing tools, we classify information through folders. An article about railway construction gets filed under ‘infrastructure’ or ‘transport’. In Evernote we tag it with ‘rail’ or ‘construction’. This is thinking like a librarian and not like a writer. We are classifying the information as an input. The reason you take notes as a writer is to produce content. It makes sense, then, to take notes in line with this goal.
Traditional filing like this tends to fail when you attempt to write your content. You are stuck trying to figure out which categories will be relevant for your proposal, paper or blog post. Interesting writing often comes from connecting separate fields through a common idea. By revealing the common denominator. By unifying two seemingly-contradictory ideas. How can you possibly achieve this if you’re looking in the same category for your information? The categories simply do not fulfil the function required by the writer.
The notes you take and indeed, the way you process information, should be with a specific project or idea in mind. You must classify information in terms of its outputs. When you take notes on a book, think about how this could apply to a specific idea you had or how it argues against a paper you read last week. The premise is that you should be organising by context and always trying to connect the dots between the content you're consuming.