IdeaWell

Project ideas from Hacker News discussions.

Pandoc Lua Filters

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1 – Perceived Bloat & Expanding Scope
"Pandoc is ever increasingly bloated?" – lifthrasiir
"A universal document converter is expected to expand via adding support for additional formats… I’m much more worried about the widening scope of the project." – lifthrasiir

Theme 2 – Value of Lua Filters
"I liked the Lua filters for solving issues on DOCX stuff for Markdown to Docx." – kalcode
"I never used luafilters before… but these days use them all the time for simple problems and am getting a clearer picture of the possibilities." – applicative

Theme 3 – Compatibility & Reactive AST Expectations
"I'm not even sure that how much of Lua scripts remain compatible across different Pandoc versions." – lifthrasiir
"If one changes something, a quick update to the AST would happen incrementally." – chaoxu

🚀 Project Ideas

Lightweight AST‑Driven Document Converter

Summary

  • A small, version‑stable engine that builds a universal document AST from any input format and emits any supported output format.
  • Eliminates redundant feature creep by exposing a minimal, well‑documented AST API for extensions.

Details

Key Value
Target Audience Developers who need reliable format conversion without Pandoc’s bloat.
Core Feature Walk through an AST, apply optional transformation plugins, emit final documents via plug‑in adapters.
Tech Stack Rust (for safety & performance), WASM for browser use, TOML‑based plugin manifest, SQLite metadata for versioning.
Difficulty Medium
Monetization Hobby

Notes

  • HN users lament Pandoc’s expanding scope and version‑compatibility headaches. This project isolates the AST, giving users a stable footprint they can control.
  • Discussing incremental AST updates (see “If one changes something, a quick update to the AST would happen incrementally.”) would spark technical debate.
  • The repo can host a community‑driven plugin marketplace for custom filters, directly addressing the Lua‑filter compatibility concerns.

Browser‑Based Pandoc Filter Playground

Summary

  • An in‑browser editor & runtime where users can write, test, and share Lua filters for Pandoc without installing anything locally.
  • Handles version‑specific filter compatibility automatically.

Details

Key Value
Target Audience Markdown writers, academic authors, and web developers seeking quick filter experiments.
Core Feature Syntax‑highlighted Lua editor, sandboxed execution against multiple Pandoc versions, live preview of HTML/PDF output.
Tech Stack React, TypeScript, LuaJIT compiled to WebAssembly, Service Workers for offline caching, Docker API for backend conversion.
Difficulty Low
Monetization Revenue-ready: SaaS subscription $5/month for premium filters and private storage.

Notes

  • Directly addresses “Lua filters have been around… What’s newer is Pandoc’s ability to be used in web browsers.” Users want an easy way to experiment without local setup.
  • The sandboxed environment can enforce version compatibility, resonating with concerns about script compatibility across Pandoc releases.
  • Opportunity for community showcases and a marketplace for popular filters, fostering discussion and utility.

Versioned Filter Compatibility Engine

Summary

  • A library that manages multiple Pandoc versions and automatically selects the appropriate filter implementation for each.
  • Provides a declarative manifest to lock filter dependencies.

Details

Key Value
Target Audience Project maintainers and CI pipelines that need reproducible document pipelines.
Core Feature Detects Pandoc version, resolves compatible Lua filter versions, caches compiled filter binaries, and offers a CLI for integration.
Tech Stack Python 3.11, PyPi packaging, YAML version manifest, SQLite for version index, GitHub Actions for CI.
Difficulty High
Monetization Revenue-ready: Enterprise support contract $1,200/year.

Notes

  • Mirrors the community worry: “how much of Lua scripts remain compatible across different Pandoc versions?” This engine solves that by enforcing explicit version pinning.
  • Could be integrated into existing static‑site generators or publishing workflows, making it a practical utility for power users.
  • Discussion around version policy and backward compatibility would likely attract both developers and maintainers of document‑conversion pipelines.

Read Later