Skip to content

Port the site documentation from APT to Markdown - #595

Merged
slachiewicz merged 2 commits into
apache:masterfrom
slachiewicz:site-apt-to-markdown
Aug 7, 2026
Merged

Port the site documentation from APT to Markdown#595
slachiewicz merged 2 commits into
apache:masterfrom
slachiewicz:site-apt-to-markdown

Conversation

@slachiewicz

Copy link
Copy Markdown
Member

Converts the site documentation under src/site/apt to Markdown. APT is a format only
Doxia understands; Markdown is already supported by maven-site-plugin out of the box,
so no POM change is needed.

Converted with doxia-converter and then cleaned up by hand: <<<code>>> becomes
backticks, <<bold>> becomes **bold**, {{{url}text}} becomes [text](url), and the
ASF licence header becomes a single block HTML comment. The page interpolates Velocity
properties, so it stays a .md.vm.

The change is split into two commits: a pure rename, so that git log --follow and
git blame still reach the page's history, and then the conversion itself. Please merge
or rebase rather than squash, or the rename is collapsed and that history is lost again.

Verified by building the site before and after the change and comparing the generated
page: the visible text and the link targets are unchanged.

Part of the wider migration tracked in
apache/maven-doxia-converter#139

A pure rename, so that git records it and `git log --follow` and `git blame` still
reach the history of each page after the conversion that follows. The content is
still APT at this point and the site does not build between the two commits.
Converted with doxia-converter and then cleaned up by hand:

- <<<code>>> becomes backticks, <<bold>> becomes **bold**, {{{url}text}}
  becomes [text](url)
- the ASF license header becomes a single block HTML comment
- the page keeps a Velocity reference, so it stays a .vm. Velocity reads ## as
  a line comment and would silently swallow every ATX heading below level one,
  so subsections use setext underlines and anything deeper is wrapped in
  #[[ ... ]]#

Verified by building the site before and after: the rendered page is
unchanged apart from <b>/<i> becoming <strong>/<em> and quotes in prose
picking up the Markdown module's typographic substitution.
@slachiewicz
slachiewicz merged commit 32a4792 into apache:master Aug 7, 2026
3 checks passed
@github-actions github-actions Bot added this to the 40 milestone Aug 7, 2026
@slachiewicz
slachiewicz deleted the site-apt-to-markdown branch August 7, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant