This is a fictional sample, not a customer project. We are the NOS Workspace team. The checks below also apply when you serve the file from ordinary static hosting.

1. Start with one file and no external dependencies

For a text-only brief, keep the styles in the document and use a system font. That removes the need to send a separate stylesheet, font file, image folder, or JavaScript bundle.

Save this as brief.html and open it in a browser:

<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Sample project brief</title>
<style>
body { margin: 0; background: #f4f5f7; color: #20242a; font: 18px/1.6 system-ui, sans-serif; }
main { max-width: 42rem; margin: 2rem auto; padding: 1.5rem; background: white; border-radius: 1rem; }
h1 { font-size: clamp(1.5rem, 5vw, 2rem); line-height: 1.2; }
</style>
</head>
<body>
<main>
<p>Fictional sample - no client data</p>
<h1>Sample project brief</h1>
<h2>Scope</h2>
<p>One project summary with a scope and a deadline.</p>
<h2>Deadline</h2>
<p>First draft: 16 October 2026</p>
</main>
</body>
</html>

The scope and deadline are ordinary text inside semantic headings and paragraphs. They do not need a framework or a build step. There is also no form submission, analytics script, or external request in this example.

This is a starting point for a document, not a replacement for an application that needs authentication, a database, or server-side behavior.

2. Keep the small-screen layout in the source

A previewer should not be expected to repair the source layout. The example includes a viewport declaration and limits the content width while allowing it to shrink:

<meta name="viewport" content="width=device-width, initial-scale=1">

main { max-width: 42rem; padding: 1.5rem; }
h1 { font-size: clamp(1.5rem, 5vw, 2rem); }

Check the actual longest heading and paragraph you intend to send. A short sample may fit when a real project name does not. Also check zoom and text wrapping; a phone-shaped preview is a useful check, but it is not a test on every phone.

We pasted the complete example into the NOS homepage editor on 9 October 2026 and checked its phone preview. The title, scope, and deadline rendered as text, with the paragraph wrapping inside the preview. That observation applies to this example; it does not establish that arbitrary imported HTML will behave the same way.

If you add an image later, revisit portability. For example:

<img src="./images/mockup.png" alt="Sample mockup">

That path expects an images folder relative to the document. Pasting the HTML into another environment does not, by itself, upload that file. Keep dependent assets available where the page will actually be viewed, and check the result rather than assuming the original folder comes along.

3. Separate checking a preview from publishing a link

Use this quick handoff checklist:

• Confirm the scope and deadline against the source material.
• Check headings and paragraphs at both a wide and narrow preview width.
• Inspect any image, stylesheet, or script dependencies you added.
• Decide whether the recipient needs a fixed snapshot or an evolving page.
• Open the eventual sharing URL while signed out before sending it.

For a fixed snapshot, make the version visible in the document:

<p>Revision 1 — fictional sample, 9 October 2026</p>

For an evolving page, keep the recipient-facing address stable and make revisions deliberately. A stable address does not mean the document is frozen.

In NOS Workspace, pasting HTML, editing visible text, and previewing can be tried from the homepage without signing in. Creating a saved sharing link is a separate step that requires an account. Shared-page readers do not need their own account. The current free plan includes three active sharing links.

Those distinctions matter during a test: seeing your file in a local preview is not proof that you have published a public URL. Test with fictional or nonsensitive material first.

References: MDN's HTML document guide, MDN's CSS guide, and MDN on clamp().

AI assisted with drafting. The sample was checked in the browser before publication.