Server-side JSX is back, and it never needed a framework
JSX was always just a nicer way to write HTML. Rendered on the server, it gives you components without shipping a single byte of JavaScript.
An overview page, a page per post and a protected form to write new posts. To keep the example free of a database, new posts are stored in a cookie in your browser, so only you can see them.
demoJSX was always just a nicer way to write HTML. Rendered on the server, it gives you components without shipping a single byte of JavaScript.
How Jeasx maps files to URLs, and why wrapping a filename in brackets is all the routing configuration you need.
Every value you put into JSX is escaped, so <script>alert('xss')</script> stays text. This post proves it.
Async components let the browser render the top of a page while the server is still waiting for slow data further down.
Where do your posts go when you hit publish? Into a signed cookie in your browser, and nowhere else.
This blog has no database. Posts you write are stored in a signed cookie in your browser, so nobody else can see them. Cookies hold only about 4 KB, so the oldest posts are dropped once it is full. You are seeing the example posts, since you haven't written a post yet.