Current directory: /home/klas4s23/domains/585455.klas4s23.mid-ica.nl/public_html/Gastenboek/uploads
## Template: HTML structure for documentation pages
Use this template to create additional documentation pages that follow the same structure and visual conventions as `stemwijzer.html`.
Copy this skeleton and replace the section content. Keep the IDs and the main class names so the project's shared scripts and styles (like `toc.js`, `search.js`, and the project's CSS) keep working.
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Page title</title>
<!-- Link the site/global stylesheet so classes like .note, .important, .code-block render correctly -->
<link rel="stylesheet" href="../../assets/css/style.css">
</head>
<body>
<!-- Accessibility fallback language toggle (visible when JS is off) -->
<div class="lang-toggle-noscript" aria-hidden="false">
<a href="page_nl.html">NL</a>
<span aria-hidden="true"> | </span>
<a href="page.html">EN</a>
</div>
<!-- Main page headings -->
<h1>Main title</h1>
<h2>Subtitle / documentation type</h2>
<!-- Table-of-contents placeholder (populated by toc.js) -->
<div id="doc-toc-placeholder" aria-hidden="true"></div>
<!-- Meta info (version/date) -->
<p><strong>Document Version:</strong> 1.0.0<br>
<strong>Last Updated:</strong> YYYY-MM-DD<br>
<strong>Document Type:</strong> Technical Reference Guide</p>
<div class="page-break"></div>
<!-- Section structure: use consistent heading levels -->
<h2>1. Section title</h2>
<h3>1.1 Subsection</h3>
<p>Intro paragraph...</p>
<!-- Small inline note -->
<div class="note">
<strong>Note:</strong> short informative text
</div>
<!-- Examples and highlighted text -->
<div class="example">
<strong>Example:</strong> describe scenario or example here
</div>
<div class="important">
<strong>Important:</strong> critical rule or warning
</div>
<!-- Use code-block for preformatted examples (SQL, JSON, PHP) -->
<div class="code-block">
-- SQL / JSON / code example here
</div>
<!-- Repeat heading levels as needed: h2, h3, h4 -->
<h2>2. Another major section</h2>
<h3>2.1 Details</h3>
<div class="page-break"></div>
<!-- Footer scripts used by the documentation pages -->
<script src="../../assets/js/toc.js"></script>
<script src="../../assets/js/search.js"></script>
</body>
</html>
```
### Conventions and class guide
- `lang-toggle-noscript`: keep for pages that need a simple, no-JS language switch.
- `page-break`: insert between large sections to control print/PDF layout.
- `note`: short informational boxes.
- `important`: warnings, rules, or must-know items.
- `example`: worked examples and scenarios.
- `code-block`: preformatted code, SQL queries, or JSON examples.
- `container`: (optional) used in some views to constrain layout — include if your page needs the same margins.
### Component includes (for CMS view pages)
If you later convert these docs into PHP view pages, the project uses components like:
- `components/position_result.php`
- `components/axis_scores.php`
- `components/political_compass.php`
- `components/position_error.php`
These are not required in pure HTML docs, but they're listed here so you know how the PHP views render the same content.
---
Next steps I can help with:
- Generate a small CSS snippet with visual styles for `.note`, `.important`, `.example`, `.code-block`, and `.page-break` (useful for new docs).
- Create a simple script to scaffold a new documentation file from this template.
If you'd like that, tell me which option and I'll add it.