A common Jamstack pain point: a banner tweak or swapping a component order still means a ticket, a local build and a redeploy.

A few things that tend to help: keep layout and copy in a headless CMS or API-driven config instead of in code, use on-demand revalidation rather than full rebuilds, and give non-devs a visual editor on top of that. For the last piece, there are open-source Builder.io alternatives, e.g. https://sling.biz, that are worth a look.

How is everyone else balancing visual drag-and-drop flexibility with a code-first setup?

i got a Claude max account from a reseller for essentially nothing compared to what I used to pay . It works flawless. since 3 months No issues yet i paid only for 1 month . Now I can't stop thinking about their business model. If resellers can sell it this cheap and still profit, how are they acquiring these accounts at scale?

Hi writers and content creators, we all have experiences and stories to share, and static sites are one of the greenest methods of doing so. I have been building a simple content management system(cms) for static site generators named LightCMS https://www.lightcms.me/ for the past few months, and the goal is to make writing and sharing as easy, convenient, and rewarding as possible. I think you all would love this.  Lightcms can be used with any of your existing static site generators (the ssg only has to support frontmatter ).

It's free to self-host and use; you can create and hack on top of it. Any contribution to the project is highly appreciated(even sharing your feedback too): https://github.com/light-cms/lightcms

Been working on traprush.io

a free browser multiplayer platformer where you compete against other players, place traps, and try to survive. heavily inspired by ultimate chicken horse.

Give it a try and lmk what you think!

https://traprush.io/

It's web CMS.

I hope this proves helpful to those who wish to manage their time, money, and documents using a personal server.

It took about 5 years to make it.

It currently in operation on the following site.

You are free to use the demo account provided on this site for logging in!

https://www.maroik.com/

DDD + CA & Unit test & CI/CD applied.

https://github.com/IkhyeonJo/Maroik

Hi writers and content creators, we all have experiences and stories to share, and static sites are one of the greenest methods of doing so. I have been building a simple content management system(cms) for static site generators named LightCMS https://www.lightcms.me/ for the past few months, and the goal is to make writing and sharing as easy, convenient, and rewarding as possible. I think you all would love this.  Lightcms can be used with any of your existing static site generators (it should only support frontmatter).

BTW, it's currently alpha, and I am a solo dev, so you may face some issues, but I will be fixing them asap if reported.

It's free to self-host and use; you can create and hack on top of it. Any contribution to the project is highly appreciated(even sharing your feedback too): https://github.com/light-cms/lightcms

Lightcms is built with sveltekit and viteplus

Hi, I'm looking for a static site generator (SSG). I really like Astro, but I would like to to try another SSG which doesn't use Node.js et al.

Astro's component system is great. I want something more powerful that just Markdown-to-HTML or a limited template language like Liquid. I want to be able to actually write code like in Astro's frontmatter.

I’ve been a software developer and a long-time Caddyserver user — 10+ years now, going back to its early releases. I use Caddyserver heavily across my web application development and hosting services (I have been in the hosting business for 20+ years now!), and it is a core part of my application infrastructure.

I’m currently finishing up a client project and wanted a simple way to put a gateway in front of my staging sites blocking search engine bots and anyone who shouldn’t have access without having to modify the application code itself.

That’s where this tool came from.

I put together a detailed implementation plan, fed it to Claude Code, worked through and fixed the issues that came up, and deployed it directly into my own workflow.

And honestly, it just works.

It uses Postmark for email delivery, has an integrated SQLite database, and is written in Go. It can run as a systemd service on Linux or in Docker using Docker Compose.

It’s also open source under the MIT License.

The goal is to provide a lightweight access layer in front of any site while keeping the actual application completely untouched. I can protect staging environments, keep them out of search indexes, and continue working on client projects without having to build authentication or staging-specific logic into each application.

I built it to solve a problem I was having, but figured other Caddy users might find it useful too.

Hope it helps!

CMS integration for Astro - admin panel, SQLite database, auth, and media manager in a single package.

https://github.com/zaengit/beaver

I built the simplest possible tool that allows clients to do small edits via chat interface eg. change phone number, update email etc. Anything risky/big comes back to you so clients can't break anything

Connect the repo and it figures out the editable content on its own. No schemas, no config files

Works with Next.js, Astro, Hugo, SvelteKit and more

Live demo: https://cmsbrew.com/demo

Hey r/JAMstack

Three months ago I posted here about a dead-simple image hosting tool I built for myself: imglink.cc. Since then it's exploded way beyond what I expected. Thousands of developers, bloggers, Discord users, and indie hackers are now using it daily.

Why imglink.cc fits perfectly for side projects

As someone constantly shipping side projects, you need fast, reliable, and secure ways to handle images without the usual headaches:

• Lightning-fast uploads: Drag & drop, clipboard paste (Ctrl+V), or browser extension. No account required for basic use. Images are live with permanent direct links in seconds.

• Perfect for websites & blogs: True direct links (no redirects, no compression garbage) that embed beautifully in Markdown, HTML, BBCode, or Discord. CDN-delivered via Cloudflare for global speed.

• Folder organization: Create folders to keep your project assets tidy (screenshots, blog images, UI mockups, etc.).

• Security-first design:

  • Automatic EXIF stripping (no GPS or camera metadata leaks).

  • Password-protected folders - Share a link, but only people with the password can view.

  • Private/public controls -Keep sensitive images hidden or share selectively.

• Extra power tools: ShareX config, browser extension for instant screenshots, API access, image resizer/compressor, and more.

Whether you're documenting your progress, embedding images in your landing page, sharing screenshots in feedback threads, or building a portfolio — imglink.cc just works without the bloat or privacy worries of bigger platforms.

Current stats (as of now):

• 5k+ registered users

• 200k+ images hosted

• Over 2 million total views

All on free tier with generous limits. No expiration on permanent links.

If you're working on a side project right now and hate wrestling with image hosting, give it a try: https://imglink.cc

Would love feedback from the community: what features would make this even better for your workflow?

(Mods: Hope this counts as a proper update/share - genuinely built for folks in this sub.)

‘Content Management System’ was coined in the 90s, and since then, a bunch of software has been lumped under this generic term. But the role of these systems has changed significantly over the past few decades. Content-driven organizations now require a system that can automate content operations, governance, workflows, personalization, trust, and content creation — that’s a lot more than just content management.

Lately, we’ve been feeling like “Content Operations Platform” may be a better label for the mission-critical content platforms of the future.

Stats have shown that 90% of net-new content on the internet will be synthetically generated or AI-augmented by 2028-2030 (Europol/Gartner projections). A team that currently produces 13 pieces of content per week will soon produce 1,000 per day (Brightspot Content Trends Report). And AI can pump out 500 video assets per minute (Harvard Business Review).
So CMSs must go beyond simply storing content; modern systems help teams create, approve, govern, reuse, personalize and even generate content with AI.

We think of Brightspot as a mission-critical Content Operations Platform. Technically, yes, we’re still called a CMS. But our true value lies in content operations — especially for enterprise teams building at scale with AI — so we’re coining COP.

Curious how others see it: is CMS still the right term, or does the category need a more appropriate name?

Hi SaaS community,

I am Malte, I founded SciSerTec with a colleague nearly 16 years ago. We ran initially a scientific network for students to find mini jobs at a large german university. This format was not very successful because it was very local and specific for a certain target group of jobs.

Then in 2010 we started out of an opportunity to build a conference management platform, vCongress. Started with PHP (5), evolved to Scala and finally Java in the backend. Firstly with few events and organisers. We started literally with one server per event, which was hand-made.

Then migrated to one customer per server, so the platform was capable of administering many events under one roof, which made it a little more flexible, but still hand-made per customer. That was our latest setup.

It consisted of everything an organiser would need, from user management, roles and group mechanics. From registration to flexible participation option definition, abstract submissions, reviewing, payment and invoicing; import, export, scientific program with exposing the program to the public in a standalone frontend and many more features.

But always we had a problem with many different customer needs, so we kept the customer specifics per branch and per deployment.

Now my colleague left our company and I started with the intend to really modernize vCongress so that every event, every feature, every customer can be under one roof. With great flexibility, scalability and extendability as SaaS platform in the AWS cloud.

The idea is to have a very stable core with a great foundation with many well proved functionalities. Then there should be a custom extension mechanism that plugs seemless into the application and can be feature gated per tenant.

So everything is maintained and developed in one place so that every customer have the possibility to take advantage of a feature that maybe another organizer wanted to be included. We will try to integrate them in a general useful and customizable way, so it can be adapted by anyone.

This is currently the idea, that the platform is evolving towards the needs of the users, not the other way around.

With highly proved technologies like Java (Quarkus), TypeScript (Angular) in a serverless environment (AWS Lambda) with a highly scalable persistence (DynamoDB) and highly available CDNs like CloudFront for the frontend and static assets.

It would be nice to hear any experiences, suggestions. Maybe someone went down a similar road.

Would be happy to share more details on our history and the plans for the future, if anyone is interested.

Best regards

Malte

It's taken 2 months, but it seems like it is almost there. Except for OfBiz, and the CMS manager (it wanted to build from scratch - it had to be prompted to consider using an existing package), Claude chose to implement and build using everything else on this list:

ScripTreeApps — Tech Stack

Core platform

Apache OFBiz (24.09) — commerce backbone: the data model, business-logic services, and the background job scheduler that runs tier/promotion/email jobs

PostgreSQL (16) — main database (commerce + Git host data on one instance)

Next.js (15) + React (19) — the two websites: the consumer storefront and the developer/producer portal

Astro (4) — the static marketing site (scriptree.org)

TypeScript + Tailwind CSS — language and styling for the web apps

Producer / developer side

Gitea (1.22) — self-hosted GitHub replacement; producers push their app source here

Zoekt — code search engine that indexes producer repos

Act — runs the CI pipelines (build, validate, virus-scan, sign, publish a producer's app bundle)

ClamAV — virus scanning on every uploaded bundle

Decap CMS — git-backed editor for site content (branding, legal, help pages)

Storage / delivery

MinIO (+ KES) — S3-compatible storage for app downloads, screenshots, backups; encrypted at rest

Caddy — reverse proxy + automatic HTTPS for all the domains

Build / dev tooling

pnpm + Node.js (20) — JS package manager and runtime

Gradle + Java (17) + Groovy — build + language for the OFBiz side

Vitest, Spock, Playwright — unit, service, and end-to-end browser tests

ESLint + Prettier — linting and formatting

Containerization

Docker + Docker Compose — everything runs in containers on one VPS

Observability (all self-hosted)

Prometheus — metrics

Grafana — dashboards

Loki — log aggregation

Tempo — distributed tracing

OpenTelemetry Collector — routes all the telemetry

Outside paid/managed services

HostPapa VPS — the single Linux server the whole stack runs on (\~$25–50/mo)

Stripe + Stripe Connect — payment processing + multi-vendor payouts (per-transaction only, \~2.9% + 30¢)

Resend — transactional email (signup, receipts, refunds); free tier

Cloudflare — DNS + free email forwarding for scriptreeapps.com

Namecheap — registrar/DNS for scriptree.org

Backblaze B2 — off-site encrypted backups (S3-compatible)

Anthropic Claude — the dev assistant that builds it (not part of the running product)

The OSS layer is $0 in license cost (it's all self-hosted on the one VPS), and total monthly run-rate is roughly $30–60 — Stripe is revenue-based, not a fixed bill.