After introducing what your project is, it's time to explain why you built it. Use about one paragraph to describe why someone should care about your project. For example:
There are a lot of ways to zip and unzip files, but they use so much memory! Zipzod is the zipping tool you need for working on low-memory devices like Raspberry Pis. I use a Raspberry Pi as a home server, and I was frustrated by my inability to easily manage large files on a small device, so I built zipzod.
Add some personal flair and motivation to this section. It should cover why you chose to build it.
- Why should only <a> and <form> be able to make HTTP requests?
- Why should only click & submit events trigger them?
- Why should only GET & POST be available?
- Why should you only be able to replace the entire screen?
By removing these arbitrary constraints htmx completes HTML as a hypertext
The development of websockets is shaped by four principles:
- Correctness: websockets is heavily tested for compliance with RFC 6455. Continuous integration fails under 100% branch coverage.
- Simplicity: all you need to understand is msg = await ws.recv() and await ws.send(msg). websockets takes care of managing connections so you can focus on your application.
- Robustness: websockets is built for production. For example, it was the only library to handle backpressure correctly before the issue became widely known in the Python community.
- Performance: memory usage is optimized and configurable. A C extension accelerates expensive operations. It's pre-compiled for Linux, macOS and Windows and packaged in the wheel format for each system and Python version.
You're trying to grab attention here, and good stories do that.
I had problem
Aand I triedBbut it didn't work becauseC. I builtDand now I can doEwith ease!