Files
fabula-ultima-html/html/15.html
Drew Malzahn c75cd188c1 feat: Add book viewer at /book with shared design system
- Add html/index.html: book viewer with auto-discovering sidebar,
  prev/next navigation, keyboard shortcuts, and URL hash persistence
- Add html/book-page.css: shared stylesheet for all book pages derived
  from fabula-ultima-sheet.css (dark theme, CSS variables, Cinzel/
  Crimson Text fonts, common class styles)
- Add book.js entry point so webpack injects the shared CSS into the
  book viewer; update webpack.config.js for two entry points, split
  CSS chunk, CopyWebpackPlugin for book pages, and /book dev server
  rewrite rule
- Add scripts/strip_watermark.py: removes "Guest Customer (Order
  #52072168)" watermark artifacts from all 210 book pages
- Add scripts/restyle_book.py: strips per-page <style> blocks and
  injects <link rel="stylesheet" href="book-page.css"> into all pages
- Update Justfile deploy to scp -r dist/* for the new /book subtree

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-06 03:36:35 +00:00

33 lines
1.7 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Document Analysis and Structure</title>
<link rel="stylesheet" href="book-page.css">
</head>
<body>
<div class="container">
<h1>Project Requirements and Structural Guidelines</h1>
<p>This document outlines the core guidelines for structuring and styling extracted textual content to ensure a professional, semantic, and highly readable web presentation.</p>
<ol>
<li data-number="1">
<strong>Semantic HTML Structure:</strong> It is critical to use appropriate HTML tags like <code>&lt;h1&gt;</code>, <code>&lt;p&gt;</code>, <code>&lt;ul&gt;</code>, <code>&lt;li&gt;</code>, and <code>&lt;strong&gt;</code>. This ensures that the underlying structure accurately reflects the content's hierarchy for maximum accessibility and SEO performance.
</li>
<li data-number="2">
<strong>Styling and Design Implementation:</strong> The presentation must incorporate styling using either inline CSS or a dedicated <code>&lt;style&gt;</code> block within the <code>&lt;head&gt;</code> section. This style guide requires modern sans-serif typography, clean margins, and a clear, predictable layout to enhance user experience.
</li>
<li data-number="3">
<strong>Output Formatting Compliance:</strong> The final deliverable must consist of <strong>ONLY valid HTML code</strong>. Under no circumstances should markdown code block backticks (<code>&lt;code&gt;&lt;/code&gt;</code>) or extra conversational commentary be included in the resulting output, maintaining purity and structural integrity.
</li>
</ol>
</div>
</body>
</html>