diff --git a/_layouts/author-docs.html b/_layouts/author-docs.html index 0cd12274..450374d0 100644 --- a/_layouts/author-docs.html +++ b/_layouts/author-docs.html @@ -27,7 +27,7 @@ - title: Auto-numbering path: /basics/numbering/ - title: Reference lookups - path: /basics/reference-lookup/ + path: /basics/reference-lookups/ - title: Cross-references path: /basics/cross-references/ - title: Terms diff --git a/_posts/2018-12-05-intro-to-metanorma.adoc b/_posts/2018-12-05-intro-to-metanorma.adoc index b5fc81a8..c34707f4 100644 --- a/_posts/2018-12-05-intro-to-metanorma.adoc +++ b/_posts/2018-12-05-intro-to-metanorma.adoc @@ -21,7 +21,7 @@ redirect_from: --- = What Metanorma is -We've said link:../../11-29-2018/writing-standards-with-metanorma/[what Metanorma is for], but we have not said much +We've said link:/blog/2018-11-29-writing-standards-with-metanorma/[what Metanorma is for], but we have not said much about what Metanorma is like as a tool. Overall, Metanorma provides three things: diff --git a/_posts/2018-12-11-writing-metanorma-in-asciidoc.adoc b/_posts/2018-12-11-writing-metanorma-in-asciidoc.adoc index 7ca68f45..ae314b85 100644 --- a/_posts/2018-12-11-writing-metanorma-in-asciidoc.adoc +++ b/_posts/2018-12-11-writing-metanorma-in-asciidoc.adoc @@ -83,7 +83,7 @@ wax polishing, instead of leaving it to the attendant. [link="/assets/blog/2018-12-11.png"] image::/assets/blog/2018-12-11-c.png[Metanorma AsciiDoc document generation as car wash] -NOTE: If you are feeling adventurous, https://github.com/metanorma/reverse_asciidoctor +NOTE: If you are feeling adventurous, https://github.com/metanorma/reverse_adoc is a tool we have created that maps HTML to Metanorma AsciiDoc, and can even be used to convert Word documents to Metanorma AsciiDoc. If you've got a lot of "`essential`" formatting, particularly mathematics, it might make sense to use it. Most of the time, though, diff --git a/_posts/2019-09-02-metanorma-now-supports-iec.adoc b/_posts/2019-09-02-metanorma-now-supports-iec.adoc index 855dacdc..64455b45 100644 --- a/_posts/2019-09-02-metanorma-now-supports-iec.adoc +++ b/_posts/2019-09-02-metanorma-now-supports-iec.adoc @@ -65,9 +65,9 @@ image::/assets/blog/2019-09-02.png[The wizard conjuring forth the IEC processor] The noteworthy differences are: * The IEC flavour uses the stage codes specific to the IEC, as listed in -https://www.iec.ch/standardsdev/resources/processes/stage_codes.htm[IEC Processes & Procedures -- Stage Codes] +https://www.iec.ch/standards-development/stage-codes[IEC Processes & Procedures -- Stage Codes] and -https://www.iec.ch/standardsdev/resources/processes/workflows.htm[IEC Processes & Procedures -- Workflow]. +https://www.iec.ch/standards-development/workflows[IEC Processes & Procedures -- Workflow]. The IEC also recognizes https://www.iso.org/stage-codes.html[ISO International Harmonized Stage Codes], which are mapped to IEC stage codes. diff --git a/_software/reverse_asciidoctor.adoc b/_software/reverse_asciidoctor.adoc index 39297fb1..ce1a9d9f 100644 --- a/_software/reverse_asciidoctor.adoc +++ b/_software/reverse_asciidoctor.adoc @@ -1,12 +1,12 @@ --- -title: reverse_asciidoctor +title: reverse_adoc description: Ruby gem to convert HTML and DOCX into AsciiDoc format. -repo_url: https://github.com/metanorma/reverse_asciidoctor +repo_url: https://github.com/metanorma/reverse_adoc external_links: - - url: https://github.com/metanorma/reverse_asciidoctor - - url: https://rubygems.org/gems/reverse_asciidoctor - - url: https://www.rubydoc.info/github/metanorma/reverse_asciidoctor/ + - url: https://github.com/metanorma/reverse_adoc + - url: https://rubygems.org/gems/reverse_adoc + - url: https://www.rubydoc.info/github/metanorma/reverse_adoc/ tags: ["writtenin:Ruby", "interface:CLI"] diff --git a/author/bsi/topics/bsiflex.png b/assets/author/bsi/topics/bsiflex.png similarity index 100% rename from author/bsi/topics/bsiflex.png rename to assets/author/bsi/topics/bsiflex.png diff --git a/author/bsi/topics/bsipas.png b/assets/author/bsi/topics/bsipas.png similarity index 100% rename from author/bsi/topics/bsipas.png rename to assets/author/bsi/topics/bsipas.png diff --git a/author/basics/cross-references.adoc b/author/basics/cross-references.adoc index f13e5832..b115e19d 100644 --- a/author/basics/cross-references.adoc +++ b/author/basics/cross-references.adoc @@ -1,10 +1,13 @@ --- layout: author-docs title: Cross-reference basics -description: This article looks at the technical details of cross-references in Metanorma AsciiDoc. If you want to learn how to insert cross-references, read link:/author/topics/inline_markup/links[Adding links and cross-references] --- == Basic anchor syntax +NOTE: This article looks at the technical details of cross-references in +Metanorma AsciiDoc. If you want to learn how to insert cross-references, read +link:/author/topics/inline_markup/links[Adding links and cross-references] + === General The basic mechanism for cross-references is setting anchors to place that should be referenced. diff --git a/author/bsi/topics/markup.adoc b/author/bsi/topics/markup.adoc index f9003951..ab2fd9a3 100644 --- a/author/bsi/topics/markup.adoc +++ b/author/bsi/topics/markup.adoc @@ -32,7 +32,7 @@ For BSI Flex: * any sponsor logo(s) at the left bottom should be provided in addition to the cover page image, * the BSI logo at the right bottom renders on-the-fly, and there no need to include it as a cover page image. -image::bsiflex.png[] +image::/assets/author/bsi/topics/bsiflex.png[] For BSI PAS: @@ -41,7 +41,7 @@ For BSI PAS: * any sponsor logo(s) at the left bottom should be provided in addition to the cover page image, * the BSI logo at the right bottom renders on-the-fly, and there no need to include it as a cover page image. -image::bsipas.png[] +image::/assets/author/bsi/topics/bsipas.png[] === Collection cover page style diff --git a/author/gb/topics/ms-word-output-caveats.adoc b/author/gb/topics/ms-word-output-caveats.adoc index a7cb29de..a11c8dd1 100644 --- a/author/gb/topics/ms-word-output-caveats.adoc +++ b/author/gb/topics/ms-word-output-caveats.adoc @@ -24,4 +24,4 @@ For that reason, those headings are instead treated by Metanorma-GB as frames (in-line with their following text), which preserve their initial spacing. -Read about Metanorma-GB's link:../topics/gbt11-compliance/[compliance with GB/T 1.1]. +Read about Metanorma-GB's link:../gbt11-compliance/[compliance with GB/T 1.1]. diff --git a/author/iec/ref/document-attributes.adoc b/author/iec/ref/document-attributes.adoc index fff2f4ec..521e16a6 100644 --- a/author/iec/ref/document-attributes.adoc +++ b/author/iec/ref/document-attributes.adoc @@ -114,8 +114,8 @@ https://www.iso.org/stage-codes.html[ISO International Harmonized Stage Codes]. The mapping to IEC stage codes is taken from https://www.iec.ch/members_experts/refdocs/iec/isoiecdir1-consolidatediecsup%7Bed15.0.RLV%7Den.pdf[ISO/IEC DIR 1:2019 + IEC SUP:2019, Annex SH], updated against the current discussion of stage codes in -https://www.iec.ch/standardsdev/resources/processes/stage_codes.htm[IEC Processes & Procedures -- Stage Codes] and -https://www.iec.ch/standardsdev/resources/processes/workflows.htm[IEC Processes & Procedures -- Workflow]. +https://www.iec.ch/standards-development/stage-codes[IEC Processes & Procedures -- Stage Codes] and +https://www.iec.ch/standards-development/workflows[IEC Processes & Procedures -- Workflow]. The following codes are supported: diff --git a/reference_docs/YAML_models/iec_document_attributes.yaml b/reference_docs/YAML_models/iec_document_attributes.yaml index 663022ee..6459b28e 100644 --- a/reference_docs/YAML_models/iec_document_attributes.yaml +++ b/reference_docs/YAML_models/iec_document_attributes.yaml @@ -48,8 +48,8 @@ document_attributes: The mapping to IEC stage codes is taken from https://www.iec.ch/members_experts/refdocs/iec/isoiecdir1-consolidatediecsup%7Bed15.0.RLV%7Den.pdf[ISO/IEC DIR 1:2019 + IEC SUP:2019, Annex SH], updated against the current discussion of stage codes in - https://www.iec.ch/standardsdev/resources/processes/stage_codes.htm[IEC Processes & Procedures -- Stage Codes] and - https://www.iec.ch/standardsdev/resources/processes/workflows.htm[IEC Processes & Procedures -- Workflow]. + https://www.iec.ch/standards-development/stage-codes[IEC Processes & Procedures -- Stage Codes] and + https://www.iec.ch/standards-development/workflows[IEC Processes & Procedures -- Workflow]. required: true example: | Following is a BPUB document in final proof (ISO stage 60, substage 00): @@ -59,7 +59,7 @@ document_attributes: :docstage: 60 :docsubstage: 00 ---- - + and this, is an NFDIS document that has reached approval stage, but it has been rejected, and will be returned to drafting: [source,asciidoc]