User:Eduralph/Sandbox/Gramps 6.0 Wiki Manual - Addon Development - Roadmap

From Gramps

← Previous · Index

Overview

Forward-looking view of the addon-development surface — what's planned, what's in flight, what's slated for deprecation, and what open questions will eventually become rules. The audience is an addon author asking "what do I need to plan around?"

This page is the prospective counterpart to What's new, which is retrospective. An item moves from this page to What's new once it ships in a release.

How to read this page

Each entry should answer four things:

Field Meaning
Status proposed / accepted / in-flight / shipped / deferred / rejected
Target Gramps version (6.1, 6.2, ...) or "unscheduled"
Impact what addon authors need to do (rewrite / opt-in / nothing)
Tracking PR / Mantis bug / wiki RFC / mailing-list thread

A roadmap entry without a tracking link is a wish, not a plan; either add the link or move the entry to a separate "ideas" section.

In flight

  • none recorded yet

Accepted but not yet implemented

  • none recorded yet

Deprecations and removals

  • none recorded yet

Open questions

  • none recorded yet

Deferred / rejected

  • none recorded yet

Documentation roadmap

The doc set itself is in flight. Pages with managed: false front-matter are draft stubs and will not appear in published output until promoted. Current draft state — flip to managed: true page by page as content lands:

Publishing-pipeline conventions (now supported)

What md2wiki.py and md2pdf.py handle as of 2026-05-30 — pages authored with these conventions render correctly in both wikitext and PDF output. Verified by running both pipelines on Gramps 6.0 Wiki Manual - Addon Development - Fundamentals (which contains an SVG embed + Obsidian-internal links).

Convention Where converted Notes
!cap Obsidian embed mdcommon.convert_obsidian_embeds Becomes ![cap](_media/foo.svg) before pandoc
Page / label Obsidian-internal link mdcommon.convert_obsidian_internal_links Resolved via mdcommon.build_title_map (filename-stem → wiki title); unresolved targets error loudly
Markdown image with SVG src in PDF _preconvert_svgs (md2pdf) Pre-converted to PDF via rsvg-convert or inkscape; embeds natively in xelatex
Markdown image with relative path in PDF --resource-path to pandoc Resolved against the source file's directory
File:Media/foo.svg post-pandoc wikitext mdcommon.basenameify_file_refs Becomes File:Foo.svg (MediaWiki's File: namespace is flat)
Media files alongside pages wikitransport.upload_if_changed + publish.upload_media_for SHA-1 dedup; uploaded BEFORE the page edit so refs never render red
HTML comments mdcommon.stash_html_comments Stashed around Obsidian preprocessors so syntax inside comments is not rewritten

What the pipeline already handled before these additions:

  • label → wikitext label / PDF anchor or external URL.
  • Template:... template shims → raw Template:... wikitext / dropped from PDF.
  • YAML front-matter → title, categories, managed.
  • Fenced code with language tags, tables.

Page-by-page draft state

(For the publishing pipeline itself — publish.py, md2wiki.py, md2pdf.py --tree — see the testbed root, not this page.)

See also

Gramps-notes.png

This article's content is incomplete or a placeholder stub.
Please update or expand this section.