points by panphora 3 days ago

I'm working on a way to make some pretty advanced software in a single HTML file.

The idea is simple: store state you'd normally store in a separate database in the document itself.

Then, also give the the document a bunch of powerful APIs granted to it by its host:

(1) Sync changes to the document with live collaborators

(2) Extract data from the document using a simple JSON map config

(3) Boot up a full content CMS from the same simple JSON map config

(4) More features added every month

I'm really excited with even the tiny bit of early traction I've gotten. About a dozen paying users so far.

Long term, I'd love to have this file type (vanilla HTML file + some extra features granted by the host) become a file type other companies offer tools and their own hosting for (like Wordpress).

Hosted platform: https://hyperclay.com

Native offline apps (source available, almost MIT license):

- https://htmlclay.com

- https://hyperclaylocal.com

octantes 21 hours ago

Hey! I've been building along the same premise but from the other side (local-first, no host). My document is a wiring canvas that can be quined or exported by removing the editor layer. Different tradeoffs from yours, but it is interesting how much it converges.

I'm curious how you solved storing state in the document. If your answer is attributes, we reached the same conclusion.

The part I've spent most of my time on is harvesting, you might find it interesting.

https://github.com/octantes/scavenger