[ 
https://issues.apache.org/jira/browse/DOXIA-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17653124#comment-17653124
 ] 

ASF GitHub Bot commented on DOXIA-617:
--------------------------------------

bertysentry commented on PR #132:
URL: https://github.com/apache/maven-doxia/pull/132#issuecomment-1367895354

   @hboutemy This is a very good point. It's better to keep backward 
compatibility as long as it doesn't make our code too complex.
   
   In this case, we could use a simple replace regex to add the `---` markers 
when we detect the old-style header. Something like 
`^(?:(\s*[a-zA-Z0-9_\-]+\s*:.*\R)+)\R(.*)` ==> `---\n$1---\n$2`
   
   (ha ha, isn't the above regex charming? 🤦‍♂️)




> doxia-module-markdown: Add support for --- header section marks
> ---------------------------------------------------------------
>
>                 Key: DOXIA-617
>                 URL: https://issues.apache.org/jira/browse/DOXIA-617
>             Project: Maven Doxia
>          Issue Type: Improvement
>          Components: Module - Markdown
>            Reporter: Bertrand Martin
>            Priority: Major
>             Fix For: 1.12.0, 2.0.0-M5
>
>
> h1. Use Case
> It is "generally" accepted that document header metadata in Markdown (like 
> _title_, _author_, etc.) must be specified inside a header section, delimited 
> with 3 hypens:
> {noformat}
> ---
> title: My Doc Title
> author: Myself
> keywords: great,doc
> ---
> # Introduction
> ...
> {noformat}
> See:
> * https://bookdown.org/yihui/rmarkdown/html-document.html
> * https://pandoc.org/MANUAL.html#extension-yaml_metadata_block
> * https://github.com/vsch/flexmark-java/wiki/Extensions#yaml-front-matter
> Currently, the only supported syntax for document header metadata is the very 
> same as above, but *without* the 3 hypens marking the header section:
> {noformat}
> title: My Doc Title
> author: Myself
> keywords: great,doc
> # Introduction
> ...
> {noformat}
> h1. Specification
> Enable the YAML Front Matter Extension of Flexmark so that such header is 
> processed automatically (nothing to code here!)
> Keep the default behavior (we want backward compatibility) with the parsing 
> of metadatas (which won't be affected by the YAML Front Matter parsing).
> h1. Doc
> Update the documentation on how to use Markdown in Doxia. This feature 
> (document metadata) is currently not documented.
> We should have a small guide on how to use Markdown in Doxia, and its 
> specific features (metadatas, macros, etc.)
> h1. Test
> Add corresponding unit tests and integration tests (for both old and new 
> syntaxes)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to