wip
This commit is contained in:
parent
f841b92802
commit
39384bb3a2
1 changed files with 9 additions and 9 deletions
|
@ -12,9 +12,9 @@
|
|||
#+begin_notes
|
||||
/TL;DR:/ [[https://brut.esy.fun][=brut.esy.fun=]]
|
||||
|
||||
*Warning*: I am not a UI developer, my choices to build this CSS Framework are certainly
|
||||
not using any current best practices, but you know: "It works for me™", so.
|
||||
Also that being said, I used this for a few different internal projects and I was happy
|
||||
*Warning*: I built this CSS Framework for my personal use.
|
||||
I am not a UI developer, and I am certainly not following best practices.
|
||||
That being said, I used this for a few different internal projects and I was happy
|
||||
enough about the result to blog about it.
|
||||
#+end_notes
|
||||
|
||||
|
@ -24,12 +24,12 @@ enough about the result to blog about it.
|
|||
#+NAME: fig:brut-homepage
|
||||
[[file:./brut-css-homepage.png]]
|
||||
|
||||
I built many private web-apps. Generally they are internal tools I built either
|
||||
for myself of for an internal team of developers.
|
||||
Along the years I started to embrace a /brutalist/ design for these tools.
|
||||
Behind the seemingly crude exterior of a brutalist website lies a system that
|
||||
strips away unnecessary elements and presents itself to users as bare-bones
|
||||
utility.
|
||||
Over the years, I've developed numerous private web applications - most often
|
||||
internal tools designed either for my own use or for an internal team of
|
||||
developers.
|
||||
While these projects have varied in scope and complexity, I've gradually come to
|
||||
appreciate the benefits of adopting a brutalist design approach for many of
|
||||
them.
|
||||
|
||||
While it's true that having both form and function is ideal, I believe there's
|
||||
value in exploring websites that prioritize UX efficiency over aesthetics.
|
||||
|
|
Loading…
Reference in a new issue