sakusei 0.3.0 → 0.5.8

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: ab634a886e4a04c4a309f672ff57317e54eab5d44e8fcac304a42c9463c5bb15
-  data.tar.gz: 4c2e2a610935627d01c80dd0f0b7ad48f6a840dddf2b433a122f4655f3a27826
+  metadata.gz: 1845947d6ebe2f9b6c5732093eff5bbd90aa7bc2a60ad79a568033bd8c674e57
+  data.tar.gz: 595a6804e797c8b0c58804b7df122b5a738e5592b786f4a0c29454801c864ed9
 SHA512:
-  metadata.gz: caf4eb2b35c3de565416c7001f5c5fb4e79837f3ddc5cb5817154b2ea4eb6e6125ad818b71520337b6381b90b9d0fd2ecbae392fe8b1d7645e41038df9d457fe
-  data.tar.gz: 579ad95d4b5a86a3095f7c6138a57bc577863cfecef7244520404bfddcd84281b9d405fbbc37053dcaf7dea6b7f8d3b81461325e186b7ba806fe547b684f96ff
+  metadata.gz: 0c2d9f30c83d0f1de7c73f8c23dcfe590208c057e95cfae0a261a64a36f7a386f3e0e34d9ba1849b46407ce4e19bd86e6dc3544db861fa8ab2f92cf0ac868d6d
+  data.tar.gz: 29428e2b7e9dbbe86753c58a537b6596f55a7ff7c075efe9bf40c1b0a2ada7d6f9921273400cc8226cf5acb12613a8caffed8ce9efc55576fe9a7d9b7790ca71

data/.claude/settings.json

@@ -0,0 +1,8 @@
+{
+  "permissions": {
+    "defaultMode": "auto",
+    "allow": [
+      "Bash(git *)"
+    ]
+  }
+}

data/.gitignore

@@ -1,5 +1,6 @@
 *.gem
 .DS_Store
 *.pdf
+!examples/*.pdf
 node_modules/
 .worktrees/

data/CLAUDE.md

@@ -0,0 +1,86 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Commands
+
+Run all tests:
+
+```bash
+bundle exec rake test
+```
+
+Run a single test file:
+
+```bash
+ruby -Ilib -Itest test/sakusei/test_builder_break_syntax.rb
+```
+
+Build and install the gem locally:
+
+```bash
+rake install
+```
+
+Build a PDF from one of the examples:
+
+```bash
+bundle exec sakusei build examples/getting-started.md
+```
+
+Live-preview a markdown file in the browser:
+
+```bash
+bundle exec sakusei-preview examples/getting-started.md
+```
+
+## Architecture
+
+Sakusei ships two CLIs:
+
+- `bin/sakusei` (Thor) — the build CLI that produces PDFs.
+- `bin/sakusei-preview` — a separate live-render binary backed by `Sakusei::PreviewServer`. Watches the source file, its `@include` partials, the active style pack, and referenced images; re-renders to HTML on change via `npx md-to-pdf --as-html` and reloads the browser tab. Loads paged.js from a CDN so `@page`/`page-break-*` rules are visible as document pages. Use this for fast iteration; use `sakusei build` for the final PDF.
+
+Both CLIs share the multi-stage build pipeline.
+
+### Build pipeline
+
+`Builder#build` in `lib/sakusei/builder.rb` runs these steps in order:
+
+1. **StylePack.discover** — walks up the directory tree from the source file, looking for `.sakusei/style_packs/<name>/` at each level. Falls back to the built-in pack at `lib/templates/default_style_pack/`.
+2. **FileResolver** — resolves `<!-- @include ./file.md -->` directives and concatenates the content.
+3. **ErbProcessor** — evaluates ERB in the markdown. Available helpers: `today(format)`, `env(name, default)`, `sh(command)`, `include_file(path)`, `image_path(relative_path)`, `document_headings(path)`.
+4. **expand_break_syntax** — expands `::break::` shorthand to `<div class="page-break"></div>`.
+5. **VueProcessor** — finds `<vue-component name="Foo" prop="value" />` tags, renders them server-side via `lib/sakusei/vue_renderer.js` using Node.js + `@vue/server-renderer` in a single batched call.
+6. **HeadingWrapper** — wraps h2/h3 headings with their immediately following content block in keep-together divs to prevent orphaned headings.
+7. **MdToPdfConverter** / **HtmlConverter** — both extend `ConverterBase` (`lib/sakusei/converter_base.rb`) and assemble the `npx md-to-pdf` command with config, stylesheets, and header/footer from the style pack. `MdToPdfConverter` runs it in a temp dir and returns the PDF path; `HtmlConverter` adds `--as-html` and returns the HTML string (used by the live preview server).
+
+`Builder#build_html` runs stages 1–6 and ends in `HtmlConverter`, sharing the pipeline with `Builder#build` so the preview matches the final PDF.
+
+`MultiFileBuilder` handles glob patterns and multiple source files, delegating to `Builder` per file and concatenating results.
+
+### Style packs
+
+A style pack is a directory containing:
+
+- `config.js` — md-to-pdf configuration (Puppeteer/Chrome options)
+- `style.css` — stylesheet applied after `lib/templates/base.css`
+- `header.html`, `footer.html` — Puppeteer page chrome injected before the markdown content
+- `components/*.vue` — Vue 3 SFCs, rendered server-side at build time (optional)
+- `package.json` — if present, npm dependencies are auto-installed on first use
+
+`lib/templates/base.css` is always applied first and provides keep-together rules for tables, code blocks, blockquotes, images, and common custom classes.
+
+Style pack discovery walks up the directory tree from the source file; a named pack can live in any ancestor's `.sakusei/` directory. The default pack in `lib/templates/default_style_pack/` is the final fallback.
+
+### Vue component system
+
+Components are referenced in markdown as `<vue-component name="MyComponent" prop="value" />`. `VueProcessor` finds all such tags in a first pass, replaces them with numbered placeholders, then sends a single JSON batch to `vue_renderer.js` via stdin. The JS renderer uses `@vue/server-renderer` to render each component and returns HTML + scoped CSS back as JSON. Scoped CSS is injected as a `<style>` block at the top of the document.
+
+Component resolution order: local `./components/<Name>.vue` → style pack `components/<Name>.vue`.
+
+Vue components support named slots via `<template #slotname>...</template>` inside the tag. Slot content is converted from Markdown to HTML before being passed to the renderer.
+
+### Tests
+
+Tests use Minitest. Fixtures live in `test/fixtures/` (markdown samples and stub style packs). `test/test_vue_renderer.js` is a standalone Node.js test for the JS renderer. The base test class `Sakusei::TestCase` provides `fixtures_dir` and a `temp_dir` that auto-cleans on teardown.

data/Gemfile.lock

@@ -0,0 +1,82 @@
+PATH
+  remote: .
+  specs:
+    sakusei (0.5.8)
+      erb (~> 4.0)
+      listen (~> 3.8)
+      thor (~> 1.2)
+      webrick (~> 1.8)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.8.9)
+      public_suffix (>= 2.0.2, < 8.0)
+    ast (2.4.3)
+    bigdecimal (4.0.1)
+    cgi (0.5.1)
+    erb (4.0.3)
+      cgi (>= 0.3.3)
+    ffi (1.17.4)
+    ffi (1.17.4-arm64-darwin)
+    json (2.19.2)
+    json-schema (6.2.0)
+      addressable (~> 2.8)
+      bigdecimal (>= 3.1, < 5)
+    language_server-protocol (3.17.0.5)
+    lint_roller (1.1.0)
+    listen (3.10.0)
+      logger
+      rb-fsevent (~> 0.10, >= 0.10.3)
+      rb-inotify (~> 0.9, >= 0.9.10)
+    logger (1.7.0)
+    mcp (0.9.0)
+      json-schema (>= 4.1)
+    minitest (5.27.0)
+    parallel (1.27.0)
+    parser (3.3.10.2)
+      ast (~> 2.4.1)
+      racc
+    prism (1.9.0)
+    public_suffix (7.0.5)
+    racc (1.8.1)
+    rainbow (3.1.1)
+    rake (13.3.1)
+    rb-fsevent (0.11.2)
+    rb-inotify (0.11.1)
+      ffi (~> 1.0)
+    regexp_parser (2.11.3)
+    rubocop (1.85.1)
+      json (~> 2.3)
+      language_server-protocol (~> 3.17.0.2)
+      lint_roller (~> 1.1.0)
+      mcp (~> 0.6)
+      parallel (~> 1.10)
+      parser (>= 3.3.0.2)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 2.9.3, < 3.0)
+      rubocop-ast (>= 1.49.0, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 2.4.0, < 4.0)
+    rubocop-ast (1.49.1)
+      parser (>= 3.3.7.2)
+      prism (~> 1.7)
+    ruby-progressbar (1.13.0)
+    thor (1.5.0)
+    unicode-display_width (3.2.0)
+      unicode-emoji (~> 4.1)
+    unicode-emoji (4.2.0)
+    webrick (1.9.2)
+
+PLATFORMS
+  arm64-darwin-24
+  ruby
+
+DEPENDENCIES
+  minitest (~> 5.0)
+  rake (~> 13.0)
+  rubocop (~> 1.0)
+  sakusei!
+
+BUNDLED WITH
+   2.7.2

data/README.md

@@ -1,14 +1,5 @@
 # Sakusei
 
-**Sakusei** (作成) — from the Japanese words meaning "creation," "making," or "craft."
-
-Like a master artisan refining their craft, Sakusei transforms raw Markdown into beautifully crafted PDF documents. Every document is an act of creation — structured, styled, and brought to life with precision.
-
-The name embodies the philosophy behind this tool: documents aren't just generated, they're _crafted_.
-
-
-## Overview
-
 Sakusei is a build system for creating PDF documents from Markdown source files. It supports:
 
 - **Markdown to PDF conversion** via `md-to-pdf`
@@ -17,16 +8,16 @@ Sakusei is a build system for creating PDF documents from Markdown source files.
 - **File inclusion** for multi-file documents
 - **PDF concatenation** for combining multiple documents
 
+---
 
-## Installation
+**Sakusei** (作成) — from the Japanese words meaning "creation," "making," or "craft."
 
-### macOS (Homebrew)
+Like a master artisan refining their craft, Sakusei transforms raw Markdown into beautifully crafted PDF documents. Every document is an act of creation — structured, styled, and brought to life with precision.
+
+The name embodies the philosophy behind this tool: documents aren't just generated, they're _crafted_.
 
-```bash
-# Add the tap and install
-brew tap keithrowell/sakusei https://github.com/keithrowell/sakusei/homebrew-tap
-brew install sakusei
-```
+
+## Installation
 
 ### Ruby Gem
 
@@ -86,6 +77,142 @@ sakusei init my_company
 sakusei concat part1.pdf part2.pdf -o combined.pdf
 ```
 
+## Examples
+
+### Basic usage
+
+Plain Markdown — headings, lists, a table, a blockquote — built with the default style pack:
+
+```markdown
+# Project Kickoff Notes
+
+**Date:** 14 April 2026
+**Attendees:** Sarah Chen, Marcus Webb, Priya Nair
+
+---
+
+## Goals for This Sprint
+
+The team aligned on three priorities for the next two weeks:
+
+1. Finalise the data model and get sign-off from the product team
+2. Stand up the staging environment so QA can begin testing early
+3. Resolve the outstanding API authentication issues before the client demo
+
+## Key Decisions
+
+- **Database:** Sticking with PostgreSQL — the migration cost to Mongo isn't justified at this scale
+- **Auth:** Moving to OAuth 2.0 with JWT refresh tokens; existing session-based auth deprecated end of month
+- **Deployment:** Staging mirrors production (same instance type, same region) to avoid environment surprises
+
+## Action Items
+
+| Owner  | Task                                | Due    |
+|--------|-------------------------------------|--------|
+| Marcus | Finalise schema and create migration | 17 Apr |
+| Priya  | Provision staging environment       | 16 Apr |
+| Sarah  | Draft OAuth integration spec        | 18 Apr |
+| All    | Review and comment on API auth RFC  | 15 Apr |
+
+> The client demo is locked in for the 25th — that date is immovable.
+> Flag anything at risk by end of day Wednesday.
+```
+
+Built with `sakusei build getting-started.md`:
+
+[![Project Kickoff Notes PDF](examples/getting-started-screenshot.png)](examples/getting-started.pdf)
+
+The full source is at [`examples/getting-started.md`](examples/getting-started.md).
+
+
+### Style packs and Vue components
+
+The source for a one-page consulting proposal, using a custom style pack with `DocMeta`, `ProcessSteps`, and `DeliverableCards` components:
+
+```markdown
+# Meridian Property Group — Operations Automation Assessment
+
+<vue-component name="DocMeta"
+  client="Meridian Property Group"
+  preparedBy="KD Consulting"
+  date="<%= today('%d %B %Y') %>"
+  status="Proposal"
+  />
+
+
+## Opportunity
+
+Meridian Property Group manages a portfolio of 340 residential and commercial tenancies
+across Southeast Queensland. The business runs on strong fundamentals, but operational
+bandwidth is a growing constraint: leasing coordinators spend the majority of their week
+on routine correspondence, manual data entry, and chasing approvals through email chains.
+This is work that AI and automation can largely eliminate.
+
+KD Consulting proposes a focused **Operations Automation Assessment** — a two-week
+engagement to map current workflows, identify the highest-impact automation opportunities,
+and deliver a clear implementation roadmap.
+
+
+## How We Work
+
+Our methodology is structured around rapid discovery and focused analysis. We do not run
+open-ended workshops or produce lengthy process documentation for its own sake. Every
+step is oriented toward the output: a prioritised set of recommendations the business
+can act on.
+
+<vue-component name="ProcessSteps" steps='[
+  {
+    "title": "Discovery",
+    "description": "Structured interviews with leasing coordinators, property managers,
+    and leadership. We map the full lifecycle of a tenancy — from enquiry through to
+    renewal or exit — and identify where time goes and where friction accumulates."
+  },
+  {
+    "title": "Analysis & Opportunity Mapping",
+    "description": "We analyse workflows against current AI and automation capabilities,
+    assessing each opportunity for feasibility, integration requirements, and business
+    impact."
+  },
+  {
+    "title": "Roadmap & Report",
+    "description": "Prioritised recommendations delivered as a practical implementation
+    roadmap — phased by effort and impact, with clear next steps for each initiative and
+    indicative investment requirements."
+  }
+]' />
+
+
+## Deliverables
+
+<vue-component name="DeliverableCards" columns="3" items='[
+  {
+    "title": "Workflow Assessment",
+    "description": "A clear map of current operations across leasing, tenancy management,
+    and communications — documenting where time is spent and where the significant
+    friction points lie."
+  },
+  {
+    "title": "Automation Opportunity Register",
+    "description": "A structured register of identified automation opportunities, each
+    assessed for business impact, implementation effort, and integration requirements
+    with existing systems."
+  },
+  {
+    "title": "Implementation Roadmap",
+    "description": "A phased, prioritised action plan with recommended sequencing,
+    indicative timelines, and investment estimates — ready to brief a delivery team or
+    internal stakeholders."
+  }
+]' />
+```
+
+Built with `sakusei build meridian-proposal.md -s kd-consulting`:
+
+[![Meridian Property Group proposal PDF](examples/meridian-proposal-screenshot.png)](examples/meridian-proposal.pdf)
+
+The full source is at [`examples/meridian-proposal.md`](examples/meridian-proposal.md).
+
+
 ## Style Packs
 
 Style packs are stored in `.sakusei/style_packs/` directories. Sakusei searches for style packs by walking up the directory tree from your source file.
@@ -126,20 +253,22 @@ Environment: <%= env('RAILS_ENV', 'development') %>
 
 ### Manual Page Breaks
 
-Insert page breaks in your markdown using HTML:
+Insert a page break with the `::break::` shorthand:
 
 ```markdown
 # Chapter 1
 
 Content here...
 
-<div class="page-break"></div>
+::break::
 
 # Chapter 2
 
 More content...
 ```
 
+This expands to `<div class="page-break"></div>` before rendering. You can also use that HTML directly if you prefer.
+
 Available classes:
 - `.page-break` or `.page-break-after` - Break after this element
 - `.page-break-before` - Break before this element

data/bin/sakusei-preview

@@ -0,0 +1,40 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require 'optparse'
+require 'sakusei'
+require 'sakusei/preview_server'
+
+options = { open: true, paged: true }
+parser = OptionParser.new do |opts|
+  opts.banner = 'Usage: sakusei-preview FILE [options]'
+
+  opts.on('-p', '--port PORT', Integer, "Port to bind (default #{Sakusei::PreviewServer::DEFAULT_PORT})") { |v| options[:port] = v }
+  opts.on('-s', '--style PACK', 'Style pack name to use') { |v| options[:style] = v }
+  opts.on('-c', '--config FILE', 'Path to md-to-pdf config file') { |v| options[:config] = v }
+  opts.on('--stylesheet FILE', 'Path to CSS stylesheet') { |v| options[:stylesheet] = v }
+  opts.on('--no-open', 'Do not open the browser automatically') { options[:open] = false }
+  opts.on('--no-paged', 'Disable paged.js pagination (show as scrolling HTML)') { options[:paged] = false }
+  opts.on('-h', '--help', 'Show this help') { puts opts; exit 0 }
+end
+
+args = parser.parse(ARGV)
+if args.empty?
+  warn parser
+  exit 1
+end
+
+source_file = args.first
+unless File.exist?(source_file)
+  warn "File not found: #{source_file}"
+  exit 1
+end
+
+begin
+  Sakusei::PreviewServer.new(source_file, options).run
+rescue Interrupt
+  exit 0
+rescue Sakusei::Error => e
+  warn "[sakusei-preview] #{e.message}"
+  exit 1
+end

data/examples/getting-started.md

@@ -0,0 +1,31 @@
+# Project Kickoff Notes
+
+**Date:** 14 April 2026  
+**Attendees:** Sarah Chen, Marcus Webb, Priya Nair
+
+---
+
+## Goals for This Sprint
+
+The team aligned on three priorities for the next two weeks:
+
+1. Finalise the data model and get sign-off from the product team
+2. Stand up the staging environment so QA can begin testing early
+3. Resolve the outstanding API authentication issues before the client demo
+
+## Key Decisions
+
+- **Database:** Sticking with PostgreSQL — the migration cost to Mongo isn't justified at this scale
+- **Auth:** Moving to OAuth 2.0 with JWT refresh tokens; existing session-based auth deprecated end of month
+- **Deployment:** Staging mirrors production (same instance type, same region) to avoid environment surprises
+
+## Action Items
+
+| Owner  | Task                               | Due    |
+|--------|------------------------------------|--------|
+| Marcus | Finalise schema and create migration | 17 Apr |
+| Priya  | Provision staging environment      | 16 Apr |
+| Sarah  | Draft OAuth integration spec       | 18 Apr |
+| All    | Review and comment on API auth RFC | 15 Apr |
+
+> The client demo is locked in for the 25th — that date is immovable. Flag anything at risk by end of day Wednesday.

data/examples/meridian-proposal.md

@@ -0,0 +1,61 @@
+# Meridian Property Group — Operations Automation Assessment
+
+<vue-component name="DocMeta"
+  client="Meridian Property Group"
+  preparedBy="KD Consulting"
+  date="<%= today('%d %B %Y') %>"
+  status="Proposal"
+  />
+
+
+Report Generated <%= today %>
+
+## Opportunity
+
+Meridian Property Group manages a portfolio of 340 residential and commercial tenancies across Southeast Queensland. The business runs on strong fundamentals, but operational bandwidth is a growing constraint: leasing coordinators spend the majority of their week on routine correspondence, manual data entry, and chasing approvals through email chains. This is work that AI and automation can largely eliminate.
+
+KD Consulting proposes a focused **Operations Automation Assessment** — a two-week engagement to map current workflows, identify the highest-impact automation opportunities, and deliver a clear implementation roadmap. The outcome is a practical action plan, not a theoretical report. Meridian's team will finish the engagement knowing exactly what to build, in what order, and what it will take to get there.
+
+
+## How We Work
+
+Our methodology is structured around rapid discovery and focused analysis. We do not run open-ended workshops or produce lengthy process documentation for its own sake. Every step is oriented toward the output: a prioritised set of recommendations the business can act on.
+
+<vue-component name="ProcessSteps" steps='[
+  {
+    "title": "Discovery",
+    "description": "Structured interviews with leasing coordinators, property managers, and leadership. We map the full lifecycle of a tenancy — from enquiry through to renewal or exit — and identify where time goes and where friction accumulates."
+  },
+  {
+    "title": "Analysis & Opportunity Mapping",
+    "description": "We analyse workflows against current AI and automation capabilities, assessing each opportunity for feasibility, integration requirements, and business impact. We distinguish quick wins from longer-horizon initiatives."
+  },
+  {
+    "title": "Roadmap & Report",
+    "description": "Prioritised recommendations delivered as a practical implementation roadmap — phased by effort and impact, with clear next steps for each initiative and indicative investment requirements."
+  }
+]' />
+
+
+## Deliverables
+
+<vue-component name="DeliverableCards" columns="3" items='[
+  {
+    "title": "Workflow Assessment",
+    "description": "A clear map of current operations across leasing, tenancy management, and communications — documenting where time is spent and where the significant friction points lie."
+  },
+  {
+    "title": "Automation Opportunity Register",
+    "description": "A structured register of identified automation opportunities, each assessed for business impact, implementation effort, and integration requirements with existing systems."
+  },
+  {
+    "title": "Implementation Roadmap",
+    "description": "A phased, prioritised action plan with recommended sequencing, indicative timelines, and investment estimates — ready to brief a delivery team or internal stakeholders."
+  }
+]' />
+
+---
+
+*This proposal is valid for 30 days from the date above. Prepared in confidence for Meridian Property Group.*
+
+**KD Consulting**

data/lib/sakusei/builder.rb

@@ -7,6 +7,7 @@ require_relative 'image_path_resolver'
 require_relative 'vue_processor'
 require_relative 'heading_wrapper'
 require_relative 'md_to_pdf_converter'
+require_relative 'html_converter'
 
 module Sakusei
   class Builder
@@ -14,45 +15,64 @@ module Sakusei
       @source_file = File.expand_path(source_file)
       @options = options
       @source_dir = File.dirname(@source_file)
+      @file_resolver = nil
+    end
+
+    attr_reader :source_file, :source_dir
+
+    # Files that contributed to the most recent build (source + @include partials).
+    # Populated after #build, #build_html, or #build_processed_content runs.
+    def resolved_input_files
+      files = [@source_file]
+      files.concat(@file_resolver.resolved_files.to_a) if @file_resolver
+      files.uniq
     end
 
     def build
-      # 1. Discover and load style pack
+      style_pack, processed_content = build_processed_content
+      $stderr.puts "[sakusei] converting to PDF..."
+      output_path = generate_output_path
+      convert_to_pdf(processed_content, output_path, style_pack)
+      $stderr.puts "[sakusei] written: #{output_path}"
+      output_path
+    end
+
+    # Run the full pipeline up to (but not including) PDF conversion, then
+    # render the processed markdown to a styled HTML string via md-to-pdf --as-html.
+    # Returns [html_string, style_pack].
+    def build_html
+      style_pack, processed_content = build_processed_content
+      html = HtmlConverter.new(processed_content, style_pack, @options.merge(source_dir: @source_dir)).convert
+      [html, style_pack]
+    end
+
+    private
+
+    def build_processed_content
       $stderr.puts "[sakusei] discovering style pack..."
       style_pack = discover_style_pack
       $stderr.puts "[sakusei] style pack: #{style_pack.name} (#{style_pack.path})"
 
-      # 2. Resolve and concatenate file references
       $stderr.puts "[sakusei] resolving file includes..."
       resolved_content = resolve_files
 
-      # 3. Process ERB templates
       $stderr.puts "[sakusei] processing ERB..."
       processed_content = process_erb(resolved_content)
 
-      # 4. Process Vue components (if available)
+      processed_content = expand_break_syntax(processed_content)
       processed_content = process_vue(processed_content, style_pack)
-
-      # 4.5 Wrap h2/h3 headings with their following block to prevent orphaned headings
       processed_content = wrap_headings(processed_content)
 
-      # 5. Convert to PDF
-      $stderr.puts "[sakusei] converting to PDF..."
-      output_path = generate_output_path
-      convert_to_pdf(processed_content, output_path, style_pack)
-
-      $stderr.puts "[sakusei] written: #{output_path}"
-      output_path
+      [style_pack, processed_content]
     end
 
-    private
-
     def discover_style_pack
       StylePack.discover(@options[:source_dir] || @source_dir, @options[:style])
     end
 
     def resolve_files
-      FileResolver.new(@source_file).resolve
+      @file_resolver = FileResolver.new(@source_file)
+      @file_resolver.resolve
     end
 
     def process_erb(content)
@@ -67,6 +87,10 @@ module Sakusei
       VueProcessor.new(content, @source_dir, style_pack: style_pack).process
     end
 
+    def expand_break_syntax(content)
+      content.gsub(/::break::/, '<div class="page-break"></div>')
+    end
+
     def wrap_headings(content)
       HeadingWrapper.new(content).wrap
     end