🔧 Programmierung 🕛 kürzlich 3 Min Lesezeit
0

PaperQuire v0.2.0 — CLI for Automating Your Docs Pipeline

↗ Quelle (dev.to)
🗣️ Stimme:
📑 Inhaltsübersicht




Your docs pipeline, from the terminal



PaperQuire v0.2.0 ships with a full command-line interface. Everything you can do in the desktop app — render, template, brand — now works from your terminal.



This means you can automate document generation, integrate PaperQuire into CI/CD pipelines, and batch-process entire directories of Markdown without opening the GUI.






Quick start



If you installed via Homebrew, the paperquire command is already on your PATH:




CODE
brew install --cask paperquire/paperquire/paperquire






Verify with:




CODE
paperquire version






The simplest render is just:




CODE
paperquire report.md






This produces report.pdf in the same directory, using the default template.






What you can do






Render with options



Apply templates, set metadata, control output:




CODE
paperquire report.md -t corporate --title "Q2 Report" --author "Jane Doe"
paperquire spec.md --page-size a4 --margins 0.75,0.75,0.75,0.75 --no-toc
paperquire draft.md --watermark "DRAFT" -o drafts/draft.pdf






All 22 flags from the desktop app's Document Setup panel are available. See the full list in the where you can browse all built-in templates and submit your own via pull request.






Project configuration



Drop a .paperquire.yml in your project root and every render in that directory picks up your settings automatically:




CODE
template: corporate
toc: true
h1-page-break: true
cover:
title: "Project Documentation"
author: "Engineering Team"
company: "Acme Corp"
branding:
primary-color: "#2563eb"






Config files are resolved in order: global (~/.paperquire/config.yml) then project (.paperquire.yml walked upward), then CLI flags win.






CI/CD integration



The CLI makes it straightforward to add document generation to your build pipeline. A GitHub Actions example:




CODE
- name: Generate docs
run: |
paperquire batch ./docs -o ./dist/docs -t corporate --continue-on-error






Use --dry-run in your CI to validate Markdown and options without producing output — useful as a pre-merge check.






What's next



This is the foundation. Future CLI updates will include watch mode for live rebuilding, PDF merge for combining multiple documents, and deeper CI integrations.






Get it





  • for the full flag and command documentation


  • Community Templates to browse and share templates



Or install via Homebrew:




CODE
brew install --cask paperquire/paperquire/paperquire


Vollständiger Original-Bericht
Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.
↗ Original-Artikel auf dev.to lesen
Wie bewertest du diesen Beitrag?
1 Klick Feedback
Teilen mit Netzwerk & Team:

Community-Analysen & Experten-Meinungen 0

Verfasse deine eigene Analyse, teile Workarounds oder diskutiere diesen Vorfall im Blog.
Noch keine Community-Analyse verfasst. Markiere einen Textabschnitt oder klicke oben auf Eigene Analyse verfassen“!
Community Pulse: Relevanz-Einschätzung
1 Klick Experten-Votum
🔴 Akute Relevanz 55%
🟡 In Evaluierung 31%
🟢 Keine Auswirkung 9%
Spannende Innovation 5%
Verwandte Story-Cluster & Quellen (Vektor-KI)
Port 8095 Engine
2 Quellen
ChatGPT, Claude, and Grok all went down at once; enterprises need a backup plan
2 Quellen
OpenAI launches GPT-6 Astra
1 Quelle
What JPMorgan does differently with AI that any company can apply
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten PaperQuire v0.2.0 — CLI for Automating Your Docs Pipeline

Thematisch verwandte Begriffe: PaperQuire, v020, Automating, Your · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...