Set up gift-guide as its own repo with a pandoc+weasyprint build pipeline
Converts the lead-magnet PDF from a Google Slides export into an editable markdown template, styled to match reground.org's dark theme, with a Makefile convention (make partners/<slug>.pdf) for producing per-partnership customized versions.
This commit is contained in:
@@ -0,0 +1,51 @@
|
||||
# Gift Guide
|
||||
|
||||
Source content and build pipeline for "How To Get Your Stories In Front Of The Readers
|
||||
Who Need Them" — the lead-magnet PDF given away at reground.org/gift. Kept in its own
|
||||
repo because this content changes on its own schedule, independent of the reground-site
|
||||
deploys.
|
||||
|
||||
Styled to match reground.org's dark theme (background, heading, and CTA colors are
|
||||
pulled directly from that site's CSS).
|
||||
|
||||
## One-time setup
|
||||
|
||||
You need `pandoc` and `weasyprint` on your `PATH`. Both are already used elsewhere on
|
||||
this machine; nothing else to install.
|
||||
|
||||
## Building a PDF
|
||||
|
||||
```sh
|
||||
make template.pdf # the generic/base version
|
||||
make partners/<slug>.pdf # a specific partnership's version
|
||||
make # rebuilds template.pdf + every partners/*.md that exists
|
||||
make clean # removes generated PDFs (never touches the .md sources)
|
||||
```
|
||||
|
||||
`make` finds the source `.md` file automatically from the `.pdf` name you ask for, so
|
||||
building any filled-in template is just naming the PDF you want.
|
||||
|
||||
## Starting a new partnership
|
||||
|
||||
```sh
|
||||
cp template.md partners/<slug>.md
|
||||
```
|
||||
|
||||
Edit the new file's title (front matter) and rewrite the opening/closing copy to bridge
|
||||
your angle with the partner's audience — the 3 Step sections and their photos are
|
||||
generally reusable as-is. Then:
|
||||
|
||||
```sh
|
||||
make partners/<slug>.pdf
|
||||
```
|
||||
|
||||
## Notes
|
||||
|
||||
- The 4 photos in `images/` were extracted from the original PDF. They're intentionally
|
||||
generic/illustrative (not specific to any one partnership) and don't need to change
|
||||
per customization.
|
||||
- `template.html` renders the cover (title + byline + author photo) from the document's
|
||||
YAML front matter — you don't need to hand-write that part in the body of each `.md`
|
||||
file, just update the front matter.
|
||||
- `style.css` is the single source of truth for the visual theme. Edit it once and
|
||||
`make all` rebuilds every partner PDF with the change.
|
||||
Reference in New Issue
Block a user