This is nice, but I don't see much of a difference between just asking claude to write a wrangler config to push to cf pages, which can be extremely simple
publishing workflow yes, i wanted to have a way to manage published urls and update existing urls with a small dashboard as well since we end up doing it repeatedly.
Remote MCP could even allow you to share it with coworkers so they don't have to run anything
I usually use Claude Code but sometimes I find myself using chat and then when it creates an artifact sometimes I just want more flexibility or less restrictions. I might be missing something but I found it surprisingly hard to actually push an artifact to a custom URL. This was okay with Netlify as a connector, but I quickly ate through the free credits.
Unfortunately the Cloudflare connector surprisingly didn't expose the way to publish a site with just static files So I ended up having Claude just write the files to a folder with a script and a wrapper worker to make it all work and then everything was manual to republish.
Seems like if you have this all bundled up via MCP you can add as connector to chat and then get the same experience. But not sure if this is over engineered or if there's an easier way.
Maybe tell your agent that your readme doesn't need to be that long so humans can read it and understand it. The Github readme is ludicrously long winded.
What's the point of this vs telling the agent to just use the cloudflare CLI?
"Local tool for publishing agent reports and small static sites" - Aren't agent reports small static sites? Why do you need to mention both?
Your Good Fits vs Bad Fits section is just a good fits vs bad fits for cloudflare pages, not your specific application.
Creating a chrome extension to add the publish button on the page is quite possibly the single biggest piece of evidence I've ever seen that code is now cheap.
Readme needs screenshots.
-----
Edit: I've been emotionally triggered by this project because the overall feel of it reminds me of all the junior developers at work who've started vibe coding everything and presenting it with confidence that even the most senior developers lack.
Yes, the readme and no screenshot was something that I meant to cleanup and add and are already live now.
Agent reports vs small static sites -> It was supposed to mean markdown files as plans gets shared between teams which is what CC mentioned as agent reports.
Yes, code is definitely cheap. Built it as an utility for myself and dogfooding it with my team. Had put it out with the thought that others might find it useful.
Point in time, a lot of it is available vanilla with cloudflare cli but natively enabling passwords, private team dashboard are something that am considering. Passwords are already live as we speak.
Will improve this as i get more feedback and time to spend on this.
This is nice, but I don't see much of a difference between just asking claude to write a wrangler config to push to cf pages, which can be extremely simple
then npx wrangler deploypublishing workflow yes, i wanted to have a way to manage published urls and update existing urls with a small dashboard as well since we end up doing it repeatedly.
MCP would be a nice addition
Remote MCP could even allow you to share it with coworkers so they don't have to run anything
I usually use Claude Code but sometimes I find myself using chat and then when it creates an artifact sometimes I just want more flexibility or less restrictions. I might be missing something but I found it surprisingly hard to actually push an artifact to a custom URL. This was okay with Netlify as a connector, but I quickly ate through the free credits.
Unfortunately the Cloudflare connector surprisingly didn't expose the way to publish a site with just static files So I ended up having Claude just write the files to a folder with a script and a wrapper worker to make it all work and then everything was manual to republish.
Seems like if you have this all bundled up via MCP you can add as connector to chat and then get the same experience. But not sure if this is over engineered or if there's an easier way.
Maybe tell your agent that your readme doesn't need to be that long so humans can read it and understand it. The Github readme is ludicrously long winded.
What's the point of this vs telling the agent to just use the cloudflare CLI?
"Local tool for publishing agent reports and small static sites" - Aren't agent reports small static sites? Why do you need to mention both?
Your Good Fits vs Bad Fits section is just a good fits vs bad fits for cloudflare pages, not your specific application.
Creating a chrome extension to add the publish button on the page is quite possibly the single biggest piece of evidence I've ever seen that code is now cheap.
Readme needs screenshots.
-----
Edit: I've been emotionally triggered by this project because the overall feel of it reminds me of all the junior developers at work who've started vibe coding everything and presenting it with confidence that even the most senior developers lack.
Thanks for the unfiltered feedback!
Yes, the readme and no screenshot was something that I meant to cleanup and add and are already live now.
Agent reports vs small static sites -> It was supposed to mean markdown files as plans gets shared between teams which is what CC mentioned as agent reports.
Yes, code is definitely cheap. Built it as an utility for myself and dogfooding it with my team. Had put it out with the thought that others might find it useful.
Point in time, a lot of it is available vanilla with cloudflare cli but natively enabling passwords, private team dashboard are something that am considering. Passwords are already live as we speak.
Will improve this as i get more feedback and time to spend on this.
Is there by chance a way to password protect the generated site?
https://github.com/robinmoisson/staticrypt
and other worse ways
yes, it is possible. Will be adding that and full website above <25mb publishing also soon
what has happened