[
https://issues.apache.org/jira/browse/MNGSITE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939882#comment-17939882
]
Herve Boutemy commented on MNGSITE-507:
---------------------------------------
where are we on this?
I'm trying to identify the remaining work, and what are the blockers.
{noformat}❯ find content/apt -name '*.apt' | wc -l
91
❯ find content/apt -name '*.apt.vm' | wc -l
41{noformat}
is everything blocked on one single missing feature in Markdown support?
Or is it a limitation on automatic conversion tooling, that requires manual
work?
> Convert APT to markdown sources
> -------------------------------
>
> Key: MNGSITE-507
> URL: https://issues.apache.org/jira/browse/MNGSITE-507
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> With the help of [doxia-converter
> 1.3|https://maven.apache.org/doxia/doxia-tools/doxia-converter/] it is now
> possible to automatically convert APT sources to markdown. In order to ease
> contribution with the well-known markdown format we should convert all APT
> sources currently located in
> https://github.com/apache/maven-site/tree/master/content/apt to markdown with
> that approach.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
