chore: framework post
This commit is contained in:
parent
4e09e604d0
commit
9dc0529b0d
2 changed files with 16 additions and 0 deletions
|
@ -3,6 +3,7 @@ export default {
|
|||
accessibility: '#Accessibility',
|
||||
development: '#WebDev',
|
||||
books: '#Books',
|
||||
css: '#CSS',
|
||||
eleventy: '#Eleventy',
|
||||
email: '#Email',
|
||||
fastmail: '#Email',
|
||||
|
|
15
src/posts/2024/you-dont-need-a-framework-for-that.md
Normal file
15
src/posts/2024/you-dont-need-a-framework-for-that.md
Normal file
|
@ -0,0 +1,15 @@
|
|||
---
|
||||
date: '2024-01-26'
|
||||
title: "You don't need a framework for that"
|
||||
description: "You don't need a framework for *any* website primarily focused on presenting information to users."
|
||||
tags: ['development', 'CSS', 'JavaScript']
|
||||
---
|
||||
You don't need a framework for *any* website primarily focused on presenting information to users.<!-- excerpt -->
|
||||
|
||||
You don't need a JavaScript framework, you don't need a CSS framework.
|
||||
|
||||
If you're operating at scale, you need accepted and agreed upon best practices for your team.
|
||||
|
||||
You might want to consider a framework if you're building a web *application*.
|
||||
|
||||
That we've spent years conflating sites and applications feels like a failure of education and imagination.
|
Reference in a new issue