201–210 of 308 posts
"With HTML, as long as you upload the file (for example to S3), you can share the link easily. Your colleagues can open it wherever they wish and easily reference it." You don't have to host html files. You can just email it and any browser can view it.
"With HTML, as long as you upload the file (for example to S3), you can share the link easily. Your colleagues can open it wherever they wish and easily reference it." You don't have to host html files. You can just email it and any browser can view it.
Heck, these days the email is the HTML
When exploring a new idea or tool, my go to prompt is ``` In a single index.html, no dependencies, sparse styling, create an app that ``` Even before AI, it's how I built small tools, and there's something lovely about being able to email my friends the tool, and tell them "If you want to make a change, toss it to your LLM!"
its super convenient to be able to throw tools like this together and load them on a static site.
When exploring a new idea or tool, my go to prompt is ``` In a single index.html, no dependencies, sparse styling, create an app that ``` Even before AI, it's how I built small tools, and there's something lovely about being able to email my friends the tool, and tell them "If you want to make a change, toss it to your LLM!"
I recommend allowing AI to use TailwindCSS and Alpine in the context, as this would generate great lightweight dynamic web pages.
My concern here is that by gravitating to HTML you lose the ability for a human (you!) to easily co-author the document with the LLM. If it’s just an explainer for your consumption, that’s not a concern - but if it’s a spec sheet for something more complex, I deeply value being able to dive in and edit what is produced for me. With a HTML doc it is much harder to do that than with MD. Now of course you could just rep…
Next up after HTML: someone rediscovers programming languages and comes up with the idea to use them to prompt agents.