bulma-templates VS htmx

If you're a beginner who wants to give it a go with bulma, or just an enthusiast who wishes to slap some content into existing template and have a web page, or maybe build some theme upon existing layout, take a look at Bulma Templates repo.

I use a simple serverside framework such as ExpressJS or FlaskJS, which routes URL requests to HTML page responses.

Served by NGINX on a Linux server. I host with DigitalOcean for $6/month

I use a CSS Framework template. I like Bulma for its simplicity: https://bulmatemplates.github.io/bulma-templates/

Summary of things to google:

- simple Serverside framework for

- Digital ocean nginx tutorial

- CSS Framework Template

I just take a Bulma template, and edit the CSS styles within its html.

If i feel ambitious, I install v/ node, then edit the sass (compiles to css)

https://bulmatemplates.github.io/bulma-templates/

Typically:

1. Generate an express app with --view=ejs (ejs is virtually the same as HTML but lets you inject js into your html)

https://expressjs.com/en/starter/generator.html

2. Display & edit a simple html page.

3. ???

4. Profit

- Web Portfolio showing 3 projects. -- for example, check out the template here [1] called "Portfolio" -- take it, repurpose it with your own content. Get it online. Add your web portfolio URL to your resume.

- Github/Gitlab (to show your code)

- LinkedIn presence

Basically: Show you have the skills. And put yourself "out there" i.e. market yourself

[1] https://bulmatemplates.github.io/bulma-templates/

The index.html file in the site folder is the landing page. The file uses the responsive Bulma CSS library that requires no JavaScript. I picked a template and modified it for this landing page.

Hi there! I want to show off a little feature I made using hanami, htmx and a little bit of redis + sidekiq.

Recently, I just rewrite one of my application Stashbin from Next.js to GO. Though my main motivation of this migration was to learn GO and experimenting with HTMX. I also aiming to reduce the resource usage of my application and simplify the deployment process. Initially, Stashbin codebase are split into two seperate repository, one for the frontend that uses Next.js and another for the backend that already uses GO. The backend repository is just a REST API responsible for storing and retreiving data from the database.

HTMX is another library that gained popularity due to its server-first approach to rendering data, although seeking a much simpler way of appealing to developers.

When I work with HTMX I need isolated component that can be reusable a form. So I create a PHP Function that generate the Input Datalist.

I was inspired by htmz (which was in turn inspired by htmx) and how the author got pretty close to a basic htmx-like experience just using an iframe. I wanted to push it a little further so whipped this demo together. My submission demonstrates progressive enhancement for the form - with js enabled the request targets an iframe that is inserted into the dom, meaning the page doesn't actually navigate (similar to event.preventDefault()). The iframe receives the html response from the request and on load triggers a function to swap out it's contents into the main page.

As described on htmx.org: "htmx gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes, so you can build modern user interfaces with the simplicity and power of hypertext"

Apart from the source code itself, the repo's README also gives a bit more details about the various packages I used.

1. htmx: https://htmx.org/

Also, there’s some response header juggling you have to do when submitting forms that have a validation step before redirecting: https://github.com/bigskysoftware/htmx/issues/369

I’ve tried to iron out any footguns or server requirements I’ve bumped into while using HTMX & Hotwire in my projects.

✨ In recent months, I have been developing web projects using GOTTHA stack: Go + Templ + Tailwind CSS + htmx + Alpine.js. As soon as I'm ready to talk about all the subtleties and pitfalls, I'll post it on my social networks.