slachiewicz opened a new pull request, #1632:
URL: https://github.com/apache/maven-site/pull/1632

   The six remaining APT pages on maven.apache.org, plus the fragment one of 
them parses. After this the site is entirely Markdown, FML and XDoc.
   
   Four pages keep their `.vm` suffix because they interpolate a version or a 
path; `guides/index.md.vm` and `guides/mini/index.md.vm` keep theirs for the 
`#set` and `#parse` directives that build the mini-guide list.
   
   Three things needed doing by hand, and each is worth knowing for anyone 
doing the same elsewhere:
   
   * Velocity reads `##` as a line comment, so every heading below level one 
would be deleted before Doxia saw the page. Level two uses a setext underline; 
deeper ones are wrapped in `#[[ ]]#`.
   * APT writes `$\{foo\}` for a reference it means to *display*, and the APT 
parser strips the backslashes — so the converted pages carried live 
`${prefix}`, `${groupId}`, `${user.home}` and `${project.version}` references. 
Those are now `${esc.d}{foo}`.
   * `mini/index.txt` is `#parse`d into what is now a Markdown page, so its APT 
comments and link syntax had to become Markdown too. It moves with the page 
that parses it, since `#parse` resolves relative to the file.
   
   Two commits: a pure `git mv` so `git log --follow` and `git blame` still 
reach each page history, then the conversion. Please **merge or rebase rather 
than squash** — squashing collapses the rename.
   
   Verified by building the site before and after and comparing all 265 
generated pages: 264 are identical in their title, author and date metadata, 
their visible text and every link target.
   
   The one difference: a Markdown table must have a header row where the APT 
table had none, so the two definition tables in the Java plugin guide gain an 
empty header. I left them empty rather than invent column headings; say the 
word if you would rather have "Element / Description" there.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to