HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
mikestefanello
pagoda
Go2022–2025
mikestefanello / pagoda

pagoda

Rapid, easy full-stack web development starter kit and admin panel in Go

7Distinct people
12Mentions
0Explicit recommenders
3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Rapid, easy full-stack web development starter kit and admin panel in Go

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 2:19:09 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year12 dated mentions

Observed mentions: 2022-01-10 13:42:21 UTC to 2025-07-30 13:27:05 UTC.

02468102022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 9 mentions; 3 submissions, 6 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC936
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

1 sources
I'll eventually make my repo public on Github, but I'm hesitant because it's still pretty half-baked. In the meantime, I'll do my best to capture the essentials. It's been a minute since I implemented it, so I apologize if I miss some details. I use the same ViewModel structure for all renders, a struct called Content. It has a members to help with rendering and whatnot, and the data being rendered in my HTML template is stored in a Data type for the content that will be displayed: Data any So whether I'm rendering complex data, a form, or just a snippet of text, that's where it lives. That allows for all sorts of patterns for rendering data and re-using templates if that's what you want to do. Or you can just keep things simple. Hat-tip to the Pagoda framework, which was used sometimes as an inspiration and other times as a guideline
Read the rest
for this (and other) patterns that I used. You can find it here: https://github.com/mikestefanello/pagoda I also have, as part of my ViewModel, a `Notifications` slice that specifies messages to send to the user and their type: Notifications []messages.Notification I have a HTML layout for my full page that includes a section that CSS uses to pick up notifications and display them via a toaster message: <div id="user-notifications" class="toaster-container"> {{ range .Notifications }} <div class="toaster{{ if .IsSuccess }} success{{ else if .IsError }} error{{ end }}"> {{ .Message }} </div> {{ end }} </div> I managed to get it working without any need for JavaScript (other than what HTMX needs to work). My partial renders use a layout that includes a section for the partially rendered code and my oob Notifications: {{ block "Content" . }} Loading content. {{ end }} <div id="user-notifications" class="toaster-container" hx-swap-oob="true"> {{ range .Notifications }} <div class="toaster{{ if .IsSuccess }} success{{ else if .IsError }} error{{ end }}"> {{ .Message }} </div> {{ end }} </div> So the hx-swap-oob results in my user-notifications <div> being replaced with new notifications content, if there is any. I have a base renderer that handles injecting the layouts and injecting data into `Notifications`. As a result, my handlers can be generally oblivious that this is all happening underneath. This model can work for updating links, updating breadcrumbs, writing messages to the console, or whatever. I'm still scratching the surface with HTMX, but I'm convinced HTMX is perfectly appropriate and a much simpler alternative for 95% of the web dev being done today.
In URL-Driven State in HTMX

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.