Sitepaste

Nov 16, 2025 update

I’ve spent some time getting mobile nice and clean with a simple editor and previewer. The editor experience can be fullscreened for easier preview or editing directly on the site. I’m going to continue iterating on it over time to get the interaction even more intuitive, especially with multimedia.

Password protected pages and sites are working smoothly. It’s one of my favorite features that I knew I wanted to build. Protecting an individual page makes it fully hidden and unreachable without the correct password which can be changed at any time. Any multimedia placed on the page is also fully hidden and only reachable with the correct password too.

Overall I’m still mapping out the most intuitive custom domains implementation for ease of use for things like emails with a clear simple UX. Other features like newsletter and customizations are mostly finished, with sending still in progress, and AI chat and comments coming after.

It’s a fun project in spare time, since I have clear goals with it, and ultimately am building something that I wish existed.

Nov 02, 2025 update

Sitepaste is now online at https://sitepaste.com, but not fully available yet. I am taking a few more weeks to get the final built sites cleaner, reduce dead bytes shipped, and add in some of the more complex features to the Pro Plan.

I’m heavily dogfooding the platform too, and may create a mirror of this blog, or even migrate this blog to the platform to test real life workflows.

The API is built out and works for workflows like GitHub action blog deployments or deploying thoughts straight from Apple Notes on iPhone. The API’s docs was the first site on the platform, and works great to help me refine theme settings.

I’ve always been a huge fan of minimal blogs that ship little to no JS and act as an archive for years without much thought. I got a bit frustrated recently with the amount of super heavy blogs and docs shipping MBs of JS for the most simple of things. I feel like there are more and more cases where I’m seeing a 5s LCP for a fully static page that hasn’t changed in months. There was a popular X post about a personal blog workflow with multiple serverless actions doing image resizing magic and a load of other things costing over $20/mo for just the image operations. That’s the kind of stuff I wanted to avoid.

There’s a strange level of overengineering in web development that is really kind of shocking once you see it, because it’s going unquestioned as the “enterprise solution.” I myself started that way by accident, having discovered high level frameworks before dialing in the fundamentals, and suffered because of it.

Sitepaste was a way to enjoy the fundamentals of the internet again, push them as far as they go, and let the users reap those benefits of simplicity whether they’re technical users or not. There are a million ways to host a simple site, but I really wanted to try adding my own way to the mix, and see what people think.

In my mind, these are static files. There’s not much of a reason to ship React to someone trying to go look at a blog post. I see it as the page they landed on is the page that should load fast, be prioritized, and not have a 5s LCP. It should be fast on 3G in a moving car, and be absolutely instant to redeploy.

In my testing, I’m able to get an average blog rebuilt and deployed in under a second. The user writes their files in markdown, adds any metadata they want with a friendly interface or with the API, save, and deploy. It’s live before they can change their browser tab.

Well, what about dynamic content? The Pro Plan pricing card promises quite a few dynamic features coming soon. That’s the next step, and it’s going to be much more complex for sure. I’m planning each of them out thoughtfully to not fall into the overengineering trap that we keep getting ourselves into in web development. This post will have more updates once these features ship.

Oct 20, 2025

Available within the next few months. It’s built to be a dead simple company docs and blog hosting solution. I’ve seen some popular solutions right now that take care of docs hosting, but use (in my opinion) the wrong tool for the job.

Docs are static files that can be changed, Sitepaste is built with this in mind. Every page should be aggressively cached at the edge, purged on modification, and hit 100% across the board in performance testing. This means any page. You’ll notice with some popular solutions, you load up some random nested page and get some massive JS chunk downloads.

Dead simple architecture, but with good modern necessities that customers expect such as FTS and add ons for enabling AI chat with docs. Able to be offered for a lot cheaper too.