Add build infrastructure and update the document with stylistic changes.

[jasonjgw]

The individual commits are as follows. The over-all effect is to set up the document build process and to make stylistic changes to the Markdown source. The README file is also updated.

• feat: create markdown version of the trust meter indroduction google doc
• Ignore generated files.
• Add a basic makefile to generate HTML, PDF and Office Open XML/Microsoft Word versions of the document.
• Add title and author metadata.
• Use separator (

  ---

  ) syntax accepted by Pandoc.
• Add editorconfig file.
• Convert the document to Markdown again, this time without line wrapping.
• Add title again after file format conversion.
• Enable section numbering for ease of reference. Clarify the makefile.
• Correct heading levels in the Definitions section.
• Use correct separator markup in the cover note.
• Refine makefile by implementing the more useful suggestions in a code review by gemini.google.com (after researching the correctness of the proposed changes).
• Update README to document the build process.

• This pull request has been tested by running npm run test without errors
• This pull request has been built by running npm run build without errors
• This isn't a duplicate of an existing pull request

Description

Steps to test

Expected behavior:

Additional information

Related issues

[CLAassistant]

All committers have signed the CLA.

[jobara]

@jasonjgw could you remove the spec file from the PR. We are planning to do the edits to that in the "draft" branch and accept comments on the #60 PR and/or issues. When this PR is in, we'll merge main into the draft branch so that you can run the makefile from that branch too.

[jasonjgw]

I've removed the draft for now as requested.

However, some of the changes were made to the draft itself. They're source formatting and markup changes, not content changes. I assume that I'll submit those in a separate PR once this ie merged.

[klown]

Thanks for this, @jasonjgw. Check out my two suggestions and let me know what you think.

[jasonjgw]

In the future, consideration should be given to using Typst rather than TeX to create PDF output. Typst is currently supported by Pandoc for PDF typesetting, but it gives an error (a known bug) with Pandoc 3.5 and Typst 0.14.2 - apparently now fixed in Pandoc but not yet in the released version.

Modern versions of TeX/LaTeX and Typst support tagged PDF (not by default in the case of LaTeX).

For purposes of this PR, I suggest no change be made.

[klown]

LGTM Thanks again @jasonjgw . I will merge this into main, and then merge main into the draft branch.