Update generated documentation for components.

Update the generated `docs/odk-workflows/components.md` file to:

* remove the bits about having to manually update the -edit file and the
  catalog file, since this is now done automatically by the ODK;
* remove the bit about having to create a custom rule to generate a
  component derived from a template, and explain instead how the ODK can
  be configured to generate such a rule automatically (`use_template`
  option);
* also show how the ODK can be configured to derive components from
  mappings or to fetch a remote component.

closes #1226

Author: gouttegd

template/_dynamic_documentation.jinja2

@@ -704,38 +704,49 @@ components:
     - filename: your-component-name.owl
 ```
 
-3) Add the component to your catalog file (src/ontology/catalog-v001.xml)
+3) Refresh your repo by running `sh run update_repo`. This will automatically (1) create a new file in `src/ontology/components/`, (2) update the `-edit` file so that it imports `{{ project.uribase }}/{% if project.uribase_suffix is not none %}{{ project.uribase_suffix }}{% else %}{{ project.id }}{% endif %}/components/your-component-name.owl` (the IRI of your new component), and (3) update the XML catalog file (`src/ontology/catalog-v001.xml`) to redirect that IRI to the file in the `src/ontology/components` directory, so that the new component can be found by tools such as Protégé or ROBOT, when they load the `-edit` file.
+
+If your component is to be generated by some automated process, add a goal in your custom Makefile (`src/ontology/{{ project.id }}.Makefile`) and make it perform any task needed to generate the component:
 
 ```
-  <uri name="{{ project.uribase }}/{% if project.uribase_suffix is not none %}{{ project.uribase_suffix }}{% else %}{{ project.id }}{% endif %}/components/your-component-name.owl" uri="components/your-component-name.owl"/>
+$(COMPONENTSDIR)/your-component-name.owl: $(SRC)
+	<Insert here the code to produce the component>
 ```
 
-4) Add the component to the edit file (src/ontology/{{ project.id }}-edit.obo)
-for .obo formats: 
+If the component is to be generated from a ROBOT template, the ODK can generate the appropriate code for you. For that, when adding the component fo the ODK configuration file (step 2 above), explicitly indicate that the component should be derived from template(s) and list the source templates:
 
 ```
-import: {{ project.uribase }}/{% if project.uribase_suffix is not none %}{{ project.uribase_suffix }}{% else %}{{ project.id }}{% endif %}/components/your-component-name.owl
+components:
+  products:
+    - filename: your-component-name.owl
+      use_template: true
+      templates:
+        - template1.tsv
+        - template2.tsv
 ```
 
-for .owl formats: 
+In this example, the component will be derived from the templates found in `src/templates/template1.tsv` and `src/templates/template2.tsv`. Initial empty templates will automatically be generated when the repository is refreshed (step 3).
+
+Likewise, the ODK can generate the required code for the case where the component is to be derived from SSSOM mappings:
 
 ```
-Import(<{{ project.uribase }}/{% if project.uribase_suffix is not none %}{{ project.uribase_suffix }}{% else %}{{ project.id }}{% endif %}/components/your-component-name.owl>)
+components:
+  products:
+    - filename: your-component-name.owl
+      use_mappings: true
+      mappings:
+        - my-mappings.sssom.tsv
 ```
 
-5) Refresh your repo by running `sh run.sh make update_repo` - this should create a new file in src/ontology/components.
-6) In your custom makefile (src/ontology/{{ project.id }}.Makefile) add a goal for your custom make file. In this example, the goal is a ROBOT template.
+and for the case where the component is to be fetched from a remote resource:
 
 ```
-$(COMPONENTSDIR)/your-component-name.owl: $(SRC) ../templates/your-component-template.tsv 
-	$(ROBOT) template --template ../templates/your-component-template.tsv \
-  annotate --ontology-iri $(ONTBASE)/$@ --output $(COMPONENTSDIR)/your-component-name.owl
+components:
+  products:
+    - filename: your-component-name.owl
+      source: https://example.org/component-source.owl
 ```
 
-(If using a ROBOT template, do not forget to add your template tsv in src/templates/)
-
-7) Make the file by running `sh run.sh make components/your-component-name.owl`
-
 ^^^ docs/odk-workflows/ManageDocumentation.md
 # Updating the Documentation