tall VS Alpine.js

Livewire will help with all the dynamic stuff. For example, create a model on the page, and have a table below populate with the new model, all without reloading. It's easy to learn as it's mostly the same syntax as Laravel itself. If you want a great pre-set framework, install this: https://github.com/laravel-frontend-presets/tall

I would recommend people that don't want the complex Jetstream bits to use this ui preset. https://github.com/laravel-frontend-presets/tall

MarkdownX is like a element with super powers ✨. It is a text editor with a beautiful interface that makes it easy for users to write in Markdown. The component has a pretty sweet dropdown that allows you to easily upload images, add lists, embed videos, and so much more!

A month ago we posted a tweet about a new editor we were building and it got a pretty huge response with nearly 500 likes and 50 retweets 🤯

That set things in motion and we started working on a version that could be used with any Tallstack application. 🙌.

I'll show you the steps below 👇 on how to install this in a new Tallstack app.

1. 🔧 Create a new Laravel App

The first step is creating a new Laravel application. If you already have an existing Tallstack application, you can skip ahead to step 3.

laravel new mdx

Enter fullscreen mode Exit fullscreen mode

In this example, I'll install a new laravel app in a folder named mdx.

Then, go into that directory cd mdx, and we can move to the next step.

2. 🔩 Installing the Tallstack Pre-set

The Tallstack preset allows us to add TailwindCSS, Alpine, and Livewire in our new application with a few simple commands. You can find that preset here: https://github.com/laravel-frontend-presets/tall.

Let's run those commands in our new application:

composer require livewire/livewire laravel-frontend-presets/tall
php artisan ui tall
npm install
npm run dev

Enter fullscreen mode Exit fullscreen mode

After we have run those commands, we should be able to visit our new site:

And we should have a new Tallstack application in front of us.

note: if you get an application key error, you may also need to run php artisan key:generate.

Next up, we'll be moving the component files to our new application.

3. 🧩 Adding the MarkdownX Editor

Adding this component to your project is literally as easy as 1, 2, 3. Because that's how many files the MarkdownX editor includes. Here are those files:

1. Controller - app/Http/Livewire/MarkdownX.php
2. View - resources/views/livewire/markdown-x.blade.php
3. Config - config/markdownx.php

After downloading a copy of the latest MarkdownX editor, you will need to move those files 👆 to their appropriate location in your Laravel application.

Note: make sure to run php artisan storage:link, if you want to test out image uploading. The MarkdownX storage uses the local public disk by default, but you can change this in the config 😉.

After you have done this, we are now ready to test it out in our new application.

🧪 Test out the Editor

To test the editor in our new app we are going to modify the welcome page located at resources/views/welcome.blade.php, to look like this:

@extends('layouts.app')

@section('content')
    
@endsection

Enter fullscreen mode Exit fullscreen mode

If we visit our application homepage we'll see the editor in front of us 🤘.

We can now drag-and-drop images, add videos, lists, and a bunch of other cool things that make writing more fun and easier than ever before.

Be sure to check out the official new landing page for MarkdownX here and the documentation here. I hope you find this component useful in your next project, and I hope you continue to build awesome stuff 🤘. See you soon!

Alpine.js for reactive frontend

✨ 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.

> But honestly, torn towards htmx but undecided.

We are in the middle of migrating from our monster react application into server rendered pages (with jinja2). The velocity at which we are able to ship and the reduction of complexity has been great so far.

Managing client side state for simple things like (is the dropdown open/closed), listening to keyboard events and such can be done with something like alpine-js [1] without all the baggage that something like react brings.

It appears this is already the trend with JS frameworks too - with server side rendering being the new norm.

[1] https://alpinejs.dev/

Sure, you can use any number of JS-avoidance libraries. I'm a fan of Turbo, and there's also htmx, Unpoly, Alpine, hyperscript, swup, barba.js, and probably others.

Direct DOM, but with a library. Specifically AlpineJS since it follows Vue closely in design practices allowing me to scale into a full web application if necessary (basically swapping to Vue takes minimal work). The Morph plugin is specifically what I like using.

If you want more details on the initial setup I encourage you to take a look at the Part I that covers more of the initial implementation. For this portion, I added Prisma as an ORM, a frontend style library called Tachyons, and AlpineJS to handle any client-side interactions. I did this to avoid needing to add a client-side bundler to the build and instead just rely on plain old module imports to compose the frontend. This is now the default for Rails and it is quite nice to not need any additional build tools for the client.

- [swallow-pywebview](https://github.com/rangwea/swallow-pywebview)： Base on [pywebview](https://pywebview.flowrl.com/) using Python，the frontend base on [alpinejs](https://alpinejs.dev/) and [tailwindcss](https://tailwindcss.com/)。

If you’ve followed our other tutorials, you might be familiar with Alpine.js. It’s a lightweight JavaScript library that allows you to add interactivity to your site without writing a single line of JavaScript. It’s incredibly easy to use, and we’ll show you how to make the animation trigger when the user scrolls to it.

The approach is not new, essentially a variation of Knockout, Alpine, and similar "JS-in-HTML" approaches.