Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Administered by:

Server stats:

2.9K
active users

c.im: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.6

#htmx

13 posts12 participants0 posts today
Public
Chris Woody Woodruff

Think server-driven web development is dead? Think again! htmx is bringing it back in style, making ASP.NET Core Razor Pages more powerful than ever. Forget the over-engineering—just clean, simple interactivity. Dive into the retro-cool magic: woodruff.dev/back-to-the-past-

Chris Woody Woodruff · Back to the Past: How htmx is Reviving Server-Driven Web Development - Chris Woody WoodruffHey folks! Welcome back to the HTMX journey. Today, we’re diving into a bit of web development history and how HTMX is taking us forward... by looking backward. Cue the DeLorean, because we’re heading back to the days when server-driven development was all the rage.
#htmx#aspnet#webdev
Public
Chris Woody Woodruff

Ditch the JavaScript overload and bring your Razor Pages to life with htmx! It’s like giving your ASP.NET Core apps superpowers—more interactivity, less hassle. Check out my latest post to see how you can level up your Razor Pages: woodruff.dev/level-up-your-raz

Chris Woody Woodruff · Level Up Your Razor Pages: Meet htmx, Your New Best Friend - Chris Woody WoodruffHey there, fellow ASP.NET developer! If you’re tired of wrestling with JavaScript frameworks or want to simplify your life, you’re in for a treat. Today, we’re diving into the wonderful world of HTMX and why it might just be the missing piece to make your ASP.NET Razor Pages even more awesome.
#htmx#aspnet#aspnetcore
Public
Chris Woody Woodruff

Code on Demand is REST’s wildcard—optional but powerful. It lets servers send executable code to clients for enhanced functionality when needed. Want to know when, why, and how to use it effectively? Check out the latest post!

htmx up next!

#REST #API #WebAPI #htmx

woodruff.dev/rest-constraint-6

Chris Woody Woodruff · REST Constraint #6: Code on Demand—When, Why, and How to Use It - Chris Woody WoodruffOf all the REST constraints, Code on Demand is the one that most developers either overlook or actively avoid. Unlike the other five constraints, it is the only optional one, meaning a RESTful system doesn’t have to use it. But when applied correctly, it can unlock powerful capabilities in web applications. Let’s explore what Code on Demand is, when it makes sense to use it, and why most REST APIs don’t rely on it.
Replied in thread
Public
Preslav Rachev

@cferdinandi good old server-side rendering with some sprinkles of #HTMX is all we’ve been doing in our projects for the past couple of years and we never looked back. Turns out (no surprises here) that the end users don’t care - they just want to get their job done. You can do a full page refresh on every click, for all they care - if it does the job, it’s rarely an issue.

Public *
peter

Just created a simple #FastAPI project to showcase how #Python server-side rendered apps with an #htmx frontend could look like, using a React-like, async, type-checked rendering engine.

The app *does not* use Jinja/Chameleon, or any similar templating engine, ugly custom syntax in #HTML -like files, etc.

Interestingly, even #ai coding assistants can pick up the patterns and offer decent completions.

You can check out the project here: github.com/volfpeter/lipsum-ch

Boost appreciated #webdev #ssr

Technology demonstration for server-side rendering with Python, FastAPI, and htmx - volfpeter/lipsum-chat
GitHubGitHub - volfpeter/lipsum-chat: Technology demonstration for server-side rendering with Python, FastAPI, and htmxTechnology demonstration for server-side rendering with Python, FastAPI, and htmx - volfpeter/lipsum-chat
ExploreLive feeds
About