feat: use new collection functionality

[ronaldtse]

Fixes #185.

Related to metanorma/metanorma-cli#205

Metanorma PR checklist

• Breaking changes (list related PRs)
• Documentation update required (create task for this)
• External dependency introduced (documentation update need)
• Gem with native library introduced

[ronaldtse]

@abunashir there are several problems with the current functionality implemented in metanorma/metanorma-cli#205.

metanorma collection collection.yaml does not work without explicit options

Right now,

bundle exec metanorma collection collection.yml
> No value provided for required options '--output-folder'

This is wrong, because the option is already provided in the collection.yaml file.

bipm-si-brochure/collection.yml

Line 30 in a588390

output_folder: brochure

Clearly the metanorma collection command is not reading the YAML options properly. This needs to be fixed.

metanorma site generate with a collection source file generates output in the wrong location

Notice that collection.yaml has this line:

bipm-si-brochure/collection.yml

Line 30 in a588390

output_folder: brochure

But the site generate command output location should override the specified output folder, because the whole point of site generate is to keep the generated output under /site/ for deployment to a website.

This case is similar to when we run the normal metanorma command:

$ metanorma compile path/document.adoc
# => generates under path/document.xml
$ metanorma site generate config.yml # which points to path/document.adoc
# => generates under site/path/document.xml

Methods to generate a defined collection

As I updated in the README, there are two ways to generate a collection.

Method 1: single command to generate the dependencies and then the collection (with the order fixed in the "site generate" file)

$ metanorma site generate -c brochure.yml --agree-to-terms

Problem: This method works, but generates the collection in the originally defined location, not the "site generate" location.

Method 2: separately compile the source components and create the collection

$ metanorma sources/si-brochure-en.adoc
$ metanorma sources/si-brochure-fr.adoc
$ mkdir -p site/documents
$ mv sources/si-brochure-en.xml site/documents
$ mv sources/si-brochure-fr.xml site/documents
$ metanorma collection collection.yml

Problem: This method is not working because of the CLI argument issue.

[ronaldtse]

Completion of this PR requires these issues fulfilled:

• metanorma collection collection.yaml does not work without explicit options metanorma-cli#283
• metanorma site generate with a collection source file generates output in the wrong location metanorma-cli#284

[abunashir]

Thanks for the all the details @ronaldtse, I guess previously I only implemented it for the site interface that might explains the first issue but I will also check the other and get back to you :)

[ronaldtse]

This works! Thank you @abunashir.

There is just one problem -- the si-brochure-en.pdf and si-brochure-fr.pdf files are compiled twice, once under site/documents and once under site/brochure, which is not ideal. Let's do that in a new ticket.

Proof: