# Single-file AI reference (Showcase v1.3)

**The only URL an AI needs is** `https://hennsa.com/style/AI_STYLE_REFERENCE.txt`.
It includes the complete design instructions, core CSS, optional showcase CSS,
copy-ready HTML structure, navigation/print JavaScript and A4 PDF guidance.
External HTML examples and the `llms.txt` index are now optional, not dependencies.

The file is deliberately published as plain text to avoid content-type restrictions
for CSS/Markdown. If a tool truncates very large text responses, check that it has
actually retrieved the full CSS sections; the individual `.txt` mirrors remain
available as a fallback. No update to IIS is required to use the new file as long
as `.txt` is served as `text/plain`.

# Carlo Hennsa — Technical Document Style Showcase

Version: 1.2 showcase · 15 October 2026  
Style guide: 1.1 · Theme: original `Carlo_Document_Theme.css`  
Prepared by: **Carlo Hennsa**

A **complete static website** containing four fictional example documents, a palette and component gallery, the style guide and CSS, and print-ready PDF editions. Everything works without any external libraries, fonts, images, analytics or API connections.

This is an **independent blue-and-gold editorial theme**. It is not official institutional branding.

## Package layout

```text
index.html                                Start here / showcase
assets/
  Carlo_Document_Theme.css                Original versioned base theme (unchanged)
  showcase.css                            Additional styles for this sample site
  site.js                                 Mobile menu, active contents navigation, print
examples/
  technical-review.html                   Technical assessment
  system-design.html                      System design specification
  decision-record.html                    Architecture decision record
  test-plan.html                          Integrated test plan
downloads/
  Carlo_Document_Style_Guide.md            Original style guide v1.1
  technical-review.pdf                    Print-ready example
  system-design.pdf                       Print-ready example
  decision-record.pdf                     Print-ready example
  test-plan.pdf                           Print-ready example
  test-plan.md                            Example content in Markdown
llms.txt                                  AI-friendly entry index
ai-style-guide.md                         Summarized AI instructions
style-manifest.json                       JSON manifest for programmatic readers
web.config                                Optional IIS MIME support for .md
README.md                                 This file
```

The separate `Carlo_Technical_Style_Standalone_Example.html` file, included next to the ZIP download but **not required by the hosted site**, is a complete standalone technical review HTML with embedded CSS and JavaScript.

## Deploy on Windows IIS

1. Extract the package into a folder on your IIS host, e.g. `D:\Sites\DocumentStyle`.
2. Open IIS Manager and choose the existing site you want to use. Add a **Virtual Directory** with alias `style` pointing to that folder, or configure an independent site and host binding.
3. Confirm the IIS **Static Content** feature is installed and the application pool or IIS identity can read this directory.
4. Open `https://YOUR-DOMAIN/style/` (or the corresponding public URL for your configuration). IIS serves `index.html` as a default document if `index.html` is enabled.
5. Open each example, test the left navigation, try a narrow/mobile screen, and confirm the four PDF links work.
6. If publishing via Cloudflare Tunnel, ensure the existing tunnel/hostname route reaches the IIS site used in step 2. This package needs no cloud configuration of its own.

**Don't overwrite an existing site's `web.config`.** The provided one is folder-scoped and only maps `.md` to a MIME type if needed for IIS. If your site already supplies that MIME type, it can be omitted. For static sites on a different web server it is unnecessary.

## Reuse for future documents

- Start from any page in `examples/`, replace fictional title, content and metadata, and link to the same two CSS files and JavaScript.
- All author fields should read **Carlo Hennsa** (or **M.C. Hennsa** for a consistently formal version).
- Keep assessment language in the first-person singular when presenting your own views.
- Keep the base theme unchanged where practical; make site-specific changes in `showcase.css`.
- Open a document and use **Print / Save PDF** in Chrome or Edge; select **A4**, enable **background graphics**, and check page breaks.
- The supplied PDFs were generated from the corresponding HTML source.

## Sharing guidance

All example projects, people counts, delivery periods, data fields, risk findings and architectural choices in this website are **illustrative**, not project evidence or validated recommendations. Replace them before using a sample as an actual deliverable.

If the domain is public, only publish documents that are intended to be public. Keep confidential client assessments and source documents in a private repository or behind an authenticated route.

## Reuse from an AI assistant

For a publicly hosted install at `https://hennsa.com/style/`, point a browsing-enabled assistant directly at **`https://hennsa.com/style/llms.txt`**. That document provides links to the full Markdown style guide, CSS, HTML examples, PDFs and a JSON manifest. Those files can be read as ordinary HTTP responses without executing JavaScript. You can also use the following prompt:

> Read https://hennsa.com/style/llms.txt and follow its links to the Markdown style guide, CSS and relevant example HTML. Create my requested document in the same Carlo Hennsa Technical Document Style; credit Carlo Hennsa and provide HTML and print-ready PDF. Do not copy the fictional facts from examples.

**Important:** This only works when the site is truly publicly reachable, HTTP access is allowed to the AI's browsing tool, and Cloudflare Access, login, bot protections or `robots.txt` do not prevent retrieval. `llms.txt` is not universally autodiscovered, especially from a `/style/` subfolder. Tell the AI the exact address. If you want root-level discovery, optionally publish an additional `/llms.txt` at the domain root linking to `/style/llms.txt` (without overwriting an existing root file). Do not publish sensitive client documents or private code along with these examples.

### v1.3: AI content-type compatibility

AI clients that refuse `text/css` or `text/markdown` should use the **identical `.txt` mirrors**. They are added as copies; do not remove or rewrite the original CSS/Markdown files.

- Main AI entry: `https://hennsa.com/style/llms.txt`
- One-request complete AI reference: `https://hennsa.com/style/AI_STYLE_REFERENCE.txt`
- Style guide mirror: `https://hennsa.com/style/downloads/Carlo_Document_Style_Guide.md.txt`
- Base CSS mirror: `https://hennsa.com/style/assets/Carlo_Document_Theme.css.txt`
- Showcase CSS mirror: `https://hennsa.com/style/assets/showcase.css.txt`
- AI guide mirror: `https://hennsa.com/style/ai-style-guide.md.txt`
- Test plan source mirror: `https://hennsa.com/style/downloads/test-plan.md.txt`

These URLs normally return `text/plain` on IIS. They do **not** bypass login, network restrictions or a domain-wide block. If you use an intermediary, test the response HTTP `Content-Type`, not just the filename.

PowerShell test after deployment (confirm HTTP 200 and `text/plain`):

```powershell
$r = Invoke-WebRequest 'https://hennsa.com/style/AI_STYLE_REFERENCE.txt'
$r.StatusCode
$r.Headers['Content-Type']

$r = Invoke-WebRequest 'https://hennsa.com/style/assets/Carlo_Document_Theme.css.txt'
$r.StatusCode
$r.Headers['Content-Type']
```

### MIME types

IIS's optional `web.config` maps `.md` to `text/markdown`. Most IIS installations serve `.txt` as text/plain and `.json` as application/json. Test these URLs after deployment. If Markdown downloads rather than displaying in your browser, an AI browser may still be able to retrieve it as bytes/text depending on its tool.

### Optional machine-readable entry files

`AI_PROMPT.txt` is a ready-to-paste example for another AI. `OPTIONAL-domain-root-llms.txt` can be renamed to `llms.txt` and deployed at the domain root **only if that root file does not already exist or has been merged**. The primary website index remains `https://hennsa.com/style/llms.txt`.

## v1.3 file additions (15 October 2026)

```text
AI_STYLE_REFERENCE.txt                       All-in-one plain-text guide + both CSS files
assets/Carlo_Document_Theme.css.txt           Core CSS exact mirror
assets/showcase.css.txt                       Extra CSS exact mirror
assets/site.js.txt                            UI JavaScript exact mirror
downloads/Carlo_Document_Style_Guide.md.txt   Full Markdown guide exact mirror
downloads/test-plan.md.txt                   Test plan Markdown exact mirror
ai-style-guide.md.txt                         AI instructions exact mirror
README.md.txt                                 README exact mirror
```

The v1.1 guide, original CSS and all HTML and PDF examples have been kept unchanged. The landing page, AI index, manifest and reuse instructions were updated. When hosting under `https://hennsa.com/style/`, upload **all files from the contents of the `Carlo-Document-Style` directory**, replacing previous site content but keeping any unrelated configuration.