I've already linked to a defense of making webapps without a build system - it really is great for long term sustainability and updates, and PHP + Vanilla JS are actually really powerful tools these days. You can even build dynamic page parts in a declarative style, using JSX looking string templates:
const list = document.getElementById("myList");
list.innerHTML = items.map((item)=>`<li>${item}</li>`).join("");
It's all right there in the browser these days!
One thing I didn't know how to do is add drag-and-drop reordering - at least not in a way that was mobile-friendly. (The browser's Drag and Drop API is one place where the usual abstraction between computers with mice or touchpads and mobile devices with touch screen breaks down.)
I knew of SortableJS but the README didn't make it clear that it works without a build system. ChatGPT straightened me out - using SortableJS is just a <script> tag away:
<script src="https://cdn.jsdelivr.net/npm/sortablejs@1.14.0/Sortable.min.js"></script>
(Hmm, there's no authentication checksum so you might want to grab the file and move it locally - I mean in general eliminating external dependencies is a good practice, tying into that long term sustainability: linkrot is real and ubiquitous, even well meaning CDNs broke projects depending on them as stuff switched from http to https...)
But back to sortable! Here's about the simplest example:
<script src="Sortable.min.js"></script>
<ol id="items-list">
<!-- List items will be dynamically inserted here -->
</ol>
<script>
document.addEventListener('DOMContentLoaded', () => {
const items = ["Apple", "Banana", "Cherry", "Date"];
const listElement = document.getElementById('items-list');
listElement.innerHTML = items.map(item => `<li>${item}</li>`).join('');
new Sortable(document.getElementById('items-list'), {
animation: 150, // Animation speed (milliseconds)
onEnd: function (evt) {
items.splice(evt.newIndex, 0, items.splice(evt.oldIndex, 1)[0]);
}
});
});
</script>
You can see it in action - everything is right there in the source.
So one slightly wonky aspect is that this kind of reverses the usual flow of declarative programming: Sortable update the DOM and then relies on the onEnd to make your internal state match. Still, a small price to pay for a mobile-friendly reordering solution; so much better than providing little /\ and \/ buttons!
You can go a little further and add some grabbable handles - here's how to make those three lines:
<span class="drag-handle">☰</span>
Add the reference to the Sortable options object:
handle: ".drag-handle",
and then a little CSS:
ul {
list-style-type: none;
padding-left: 0;
}
.drag-handle {
cursor: grab; /* Changes the cursor to indicate movability */
padding-right: 10px; /* Spacing between the handle and the text */
user-select: none; /* Prevents text selection */
}
/* Style the drag handle on hover and active states for better feedback */
.drag-handle:hover, .drag-handle:active {
cursor: grabbing;
}
Here's a working example of that.
Finally, if you DO rerender the list, you should probably hold onto the returned Sortable object and call .destroy() and then reapply. That's obviously more tied into whatever app you're actually making, but here is a basic destroy/rerender example as well, which is a bit closer to my usecase.
