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).
Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Deliver early and continuously
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements
Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
Self-organizing teams
The best architectures, requirements, and designs emerge from self-organizing teams.
Technical excellence and good design
Continuous attention to technical excellence and good design enhances agility.
Agility and sustainability
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
The amount of work not done
Simplicity—the art of maximizing the amount of work not done—is essential.
The primary measure of progress
Working software is the primary measure of progress.
Build projects around motivated individuals
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
Deliver working software frequently
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers
Business people and developers must work together daily throughout the project.
Face-to-face conversations
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Reflect, tune, adjust
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.