Site generation: RFC documents not showing HTML in site generate

[ronaldtse]

This blocks:

• Metanorma site generation not showing HTML outputs for RFCs CalConnect/PUBLIC_DRAFTS#25

In this action:
https://github.com/CalConnect/PUBLIC_DRAFTS/actions/runs/4071026113

The generated site looks like this:

Notice that the HTML output is missing, and therefore the title does not link anywhere:

However, in the generated site artifact, the HTML is included:

This is clearly a bug with the site generation code that it cannot find the generated HTML output.

@abunashir @CAMOBAP can you please help address this? Thanks.

[abunashir]

I'm looking into it 👍🏼

[abunashir]

Looks like this issue similar to #257, a missing rxl extension was causing the issue. I've added a PR to address this issue. Here is how that should look like:

But I also see one more issue with the second document draft-ietf-calext-ical-tasks.rfc.xml, which has xml extension, so I think the collection interface is picking that up but it doesn't have corresponding html or other file, so how should we process that one? what's the expected behaviour here?

[ronaldtse]

The .rfc.xml file is the IETF RFC XML format, which is necessary for the generation of the HTML (the HTML is generated using IETF's xml2rfc command-line tool).

Technically, the document generation process of Metanorma should provide a YAML structure for each of the files for the rendering of the mini-site, e.g.:

- file: draft-ietf-calext-ical-tasks.html
  format: html
  format_name: HTML
- file: draft-ietf-calext-ical-tasks.xml
  format: xml
  format_name: Metanorma Semantic XML
- file: draft-ietf-calext-ical-tasks.rfc.xml
  format: xml
  format_name: IETF RFC XML
...

It is also strange that we require the generation of the rxl file, this is something we have to fix. I think the document generation process should create a index.yaml file that contains the metadata of all files generated.