Skip to content

Port the site documentation from APT to Markdown - #1006

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

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

Conversation

@slachiewicz

Copy link
Copy Markdown
Member

Converts the 22 pages 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.

The pages were converted with doxia-converter and then cleaned up by hand:

  • <<<code>>> becomes backticks, <<bold>> becomes **bold**, and
    {{{url}text}} becomes [text](url)
  • the ASF licence header becomes a single block HTML comment
  • a page whose only Velocity reference was ${project.name} is now a plain
    .md with the title spelled out
  • a page that keeps a reference 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
    #[[ ... ]]#
  • a reference the page means to display rather than resolve is written
    ${esc.d}{...}

Verified by building the site before and after the change and comparing every
generated page. The visible text and the link targets are unchanged, apart
from <b>/<i> rendering as <strong>/<em> and quotes and ellipses in
prose picking up the Markdown module's typographic substitution.

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.
22 page(s) 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
- a page whose only Velocity reference was ${project.name} is now a plain
  .md with the title spelled out
- a page that keeps a reference 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 and comparing every generated
page: the visible text and the link targets are unchanged apart from
<b>/<i> becoming <strong>/<em> and quotes and ellipses in prose picking up
the Markdown module's typographic substitution.

The one remaining difference is a fix: the plugin specification page wrote
<<<${target.groupId}>>>, and APT parsed the braces as an anchor definition,
so the old page rendered "$target.groupId" with the braces swallowed. The
Markdown page renders the literal ${target.groupId} that was meant.
@slachiewicz
slachiewicz force-pushed the site-apt-to-markdown branch from 46a3575 to 2a3d9df Compare August 6, 2026 12:49
@slachiewicz
slachiewicz merged commit e4e44ab into apache:master Aug 6, 2026
17 checks passed
@slachiewicz
slachiewicz deleted the site-apt-to-markdown branch August 6, 2026 17:15
@github-actions github-actions Bot added this to the 3.4.2 milestone Aug 6, 2026
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