2 ms·

Ah. You won't like https://motherfuckingwebsite.com/ https://motherfuckingwebsite.com/ then. I use it as a showcase of how to make simple websites when they ne

Ah. You won't like https://motherfuckingwebsite.com/ https://motherfuckingwebsite.com/ then. I use it as a showcase of how to make simple websites when they need to be simple.

KronisLV 5y ago
Don't forget about the spinoffs: 1) http://bettermotherfuckingwebsite.com/ http://bettermotherfuckingwebsite.com/ 2) https://thebestmotherfucking.website/ https://thebestmotherfucking.website/ Personally, i think that the sweet spot lies somewhere in the middle: - use a basic CSS framework to save time on design but without introducing too much bloat (e.g. Skeleton or PureCSS come to mind, maybe Bootstrap if you really really want to, instead of something heavier like Foundation) - focus on simplicity in your site, don't get too caught up with dynamic elements (e.g. more like documents/forms rather than a visual experience) - if you need complex form validations, you may use something like Vue, but consider proper bundle splitting; alternatively just do server side rendering if that's acceptable (especially if you want to support your site being used without JS) - don't forget that you'll still absolutely be judged by your users - sites that look too old timey might just turn off some users from using your thing, just the way things are Here's a nice presentation about website bloat (from 7 years ago, though little has changed): https://idlewords.com/talks/website_obesity.htm https://idlewords.com/talks/website_obesity.htm Here's my boring homepage, for example: https://kronis.dev/ https://kronis.dev/ The heaviest thing on it probably is the icon font (a legacy from the days past, from the Materialize library, instead of just SVG icons or even emojis), but it would absolutely exclude me from many front-end dev/designer positions (apart from the HTML/CSS being lazily written, of course).
- BrandoElFollito 5y ago
  Yes, I should have added them, thanks. The second one is the one I am for. When I finally start my blog (a 15 years effort so far) I will use that style. I find the messy one too loaded :)
taylorportman 5y ago
The (food!)recipe site I find myself frequenting lately is: https://www.tfrecipes.com/vmlinux-error-137/ https://www.tfrecipes.com/vmlinux-error-137/

Ah. You won't like https://motherfuckingwebsite.com/ https://motherfuckingwebsite.com/ then. I use it as a showcase of how to make simple websites when they need to be simple.

KronisLV 5y ago

Don't forget about the spinoffs: 1) http://bettermotherfuckingwebsite.com/ http://bettermotherfuckingwebsite.com/ 2) https://thebestmotherfucking.website/ https://thebestmotherfucking.website/ Personally, i think that the sweet spot lies somewhere in the middle: - use a basic CSS framework to save time on design but without introducing too much bloat (e.g. Skeleton or PureCSS come to mind, maybe Bootstrap if you really really want to, instead of something heavier like Foundation) - focus on simplicity in your site, don't get too caught up with dynamic elements (e.g. more like documents/forms rather than a visual experience) - if you need complex form validations, you may use something like Vue, but consider proper bundle splitting; alternatively just do server side rendering if that's acceptable (especially if you want to support your site being used without JS) - don't forget that you'll still absolutely be judged by your users - sites that look too old timey might just turn off some users from using your thing, just the way things are Here's a nice presentation about website bloat (from 7 years ago, though little has changed): https://idlewords.com/talks/website_obesity.htm https://idlewords.com/talks/website_obesity.htm Here's my boring homepage, for example: https://kronis.dev/ https://kronis.dev/ The heaviest thing on it probably is the icon font (a legacy from the days past, from the Materialize library, instead of just SVG icons or even emojis), but it would absolutely exclude me from many front-end dev/designer positions (apart from the HTML/CSS being lazily written, of course).

BrandoElFollito 5y ago
Yes, I should have added them, thanks. The second one is the one I am for. When I finally start my blog (a 15 years effort so far) I will use that style. I find the messy one too loaded :)

taylorportman 5y ago

The (food!)recipe site I find myself frequenting lately is: https://www.tfrecipes.com/vmlinux-error-137/ https://www.tfrecipes.com/vmlinux-error-137/