Moonacres Text-to-HTML Conversion Standard (MTHCS)

Purpose

This document defines the [Moonacres Text-to-HTML Conversion Standard] (MTHCS). Its purpose is to convert operational and standards-based plain-text documents into HTML in a predictable, minimal, readable, and maintainable format. The rules below follow the Plain-Text House Style (Setext-style) v6 and specify how each textual construct should appear in HTML.

Scope

The MTHCS applies to all converted standards, processes, and reference documents stored under:

systems/standards/
systems/processes/

It covers everyday operational documents, process tasks, and system references.

Overview

The core principle of the MTHCS is *minimalism*: convert text into HTML only to the extent required for consistent rendering, clarity, and collapsibility. All other semantics, spacing, and layout conventions must reflect the behaviour seen in manually curated HTML exemplars.

1. Document Structure

All converted documents must follow a simple HTML envelope:

<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <title>Title goes here</title>
  <link rel="stylesheet" href="../css/moonacres_process.css">
</head>
<body>
  <h1>Title goes here</h1>
  ... rest of content ...
</body>
</html>

No additional metadata, JavaScript, or structural elements may be inserted unless explicitly required.

2. Headings

<h1> remains literal in the HTML.
<h2> becomes a collapsible block:
<details class="details-level-1"><summary>Title</summary>...</details>
<h3> becomes:
<details class="details-level-2"><summary>Title</summary>...</details>

No <h2> or <h3> tags remain in converted files. Summary text must be plain text, not wrapped inside heading tags.

There must be no <p> tags around section titles.

3. Paragraphs

Paragraphs should normally be represented as plain text within a section. Use <p> only when the paragraph is semantically distinct and benefits from additional spacing (for example, the Author/Date header block). Overuse of <p> adds unwanted vertical space and must be avoided.

4. Lists

Bulleted lists become <ul>. Numbered lists become <ol>. Lettered lists use <ol type="a">.

Each <li> contains plain text only. Do not wrap list items in <p>.

5. Defined Terms

Defined Terms remain literal in HTML:

[Defined Term]

Do not convert these into styled spans or semantic tags.

6. Preformatted Blocks

ASCII tables, code blocks, and literal examples become:

<pre><code>
...
</code></pre>

Never wrap <pre> inside <p> or inside additional containers.

7. Vertical Spacing

Spacing must be controlled by CSS and structural elements. Avoid adding extra <p> tags or redundant <br> breaks. Only use <br> for necessary single-line intentional breaks inside narrative text.

8. Collapsible Sections

All major sections must be wrapped in <details>. The nesting level is determined by the heading level:

H2 → details-level-1
H3 → details-level-2
H4 → details-level-3 (future use)

Example:

<details class="details-level-1" open>
  <summary>Section Title</summary>
  Section content...
</details>

The summary must contain only the title text.

9. Inline Formatting

Asterisks and emphasis markers remain literal:

*note*, **warning**, etc.

Do not convert these to <em> or <strong> unless explicitly instructed.

10. File Names

All converted documents should follow the pattern:

<name>_process.html
<name>_standard.html

Names must be lowercase, with underscores for spaces.

Checklist

Heading conversion performed.
No <h2>/<h3> tags remain.
<p> used only where appropriate.
Lists converted properly.
Pre/code preserved.
Sections wrapped in details/summary.
CSS link included.
ASCII-only maintained.

Moonacres Text-to-HTML Conversion Standard (MTHCS)

Steps