The last mile of publishing: turning article headings into Gutenberg image plans

When an article is ready to publish, the visual work is often not finished.

At Yoldaolmak.com, I kept seeing the same manual loop: find an image that fits each section, check its license, write alt text and a caption, upload it to WordPress, and place the Gutenberg block at the right point. It is repetitive work, but the mistakes are not small: skipped alt text, unclear provenance, and images that do not match the section they sit beside.

I built Pictovap to make that last mile an inspectable workflow:

Markdown or Gutenberg HTML
  -> Visual Brief
  -> candidate Fit Scores
  -> Provenance Pack
  -> CMS Placement plan
  -> editor-readable report

The important design choice is that the output is a plan before it is a publish action. An editor can review the selected image, the reason it fits, the license and attribution fields, the generated metadata, and the target placement before a CMS adapter writes anything.

The demo has no API keys and makes no network calls:

pip install pictovap
pictovap demo

WordPress/Gutenberg is the first integration, but the core stays adapter-based: image sources, CMS targets, renderers, and publisher profiles are public extension points. The project also includes a side-effect-free validator and an audit command for coverage, provenance, alt text, review queues, and duplicate selections.

If you build Markdown-to-WordPress tooling, Gutenberg workflows, media-library automation, or another CMS adapter, I would value practical feedback on where this visual-planning boundary fits your workflow.

Repository: https://github.com/yoldaolmak/Pictovap
Framework guide: https://github.com/yoldaolmak/Pictovap/blob/main/docs/framework.md