- Source URL
- https://nos-workspace.com
- Affiliation / Disclosure
- Creator. This is the official NOS Workspace account, run by the maker of NOS (https://nos-workspace.com). The post links only to the official site and has no referral or affiliate links. Drafted with help from Claude.
I'm the maker of NOS (Everything is HTML now. Give it a home), and this is the official NOS account. NOS is for a specific moment: you have a report or a one-page presentation as an HTML file, written by hand or produced by an AI tool, and just before sending it you spot a wrong date or a sentence that reads badly.
You paste the HTML into NOS and see the rendered page. Click the text you want to change and type the fix. The change is written back into the original HTML, so you don't have to open the code or ask the AI to regenerate the file.
Then you share it as a NOS link. There is no separate website to deploy. You need an account to save and share; the person you send it to opens the link without logging in. If you fix something later, it's still the same link, so you don't resend a new file.
Because NOS is a workspace for documents and HTML, the report can sit next to the notes behind it instead of getting lost in a downloads folder or chat thread.
A question for people here who get HTML reports or presentations out of AI or automation workflows: after the file is generated, what do you usually still fix by hand before it goes to the reader? I drafted this post with help from Claude and checked the product details against the current site.
You paste the HTML into NOS and see the rendered page. Click the text you want to change and type the fix. The change is written back into the original HTML, so you don't have to open the code or ask the AI to regenerate the file.
Then you share it as a NOS link. There is no separate website to deploy. You need an account to save and share; the person you send it to opens the link without logging in. If you fix something later, it's still the same link, so you don't resend a new file.
Because NOS is a workspace for documents and HTML, the report can sit next to the notes behind it instead of getting lost in a downloads folder or chat thread.
A question for people here who get HTML reports or presentations out of AI or automation workflows: after the file is generated, what do you usually still fix by hand before it goes to the reader? I drafted this post with help from Claude and checked the product details against the current site.