From c7cd1fef32269faf7b56a201638f0c7c3829592c Mon Sep 17 00:00:00 2001 From: eggy Date: Mon, 31 Oct 2022 14:20:04 -0400 Subject: [PATCH] fix: add blog excerpt --- content/blog/2022/why-use-web-frameworks.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/blog/2022/why-use-web-frameworks.md b/content/blog/2022/why-use-web-frameworks.md index 33b5686..290eb08 100644 --- a/content/blog/2022/why-use-web-frameworks.md +++ b/content/blog/2022/why-use-web-frameworks.md @@ -10,6 +10,8 @@ This article is [also published in *The FOSS Albatross*](https://medium.com/the- You're a web developer and you need to make a website. How should you build one? Do you start writing static files right away to be served immediately, or do you start setting up a project environment? + + First, do you decide to use a framework? They're all the rage these days. By far the biggest advantage of a web framework is its ability to make things declarative. Imagine you want to make a to-do list. You might write code like this to be able to add a new todo: