Add build instructions for quarto-web to README

[cwickham]

For example:

• What version of quarto to use: dev

• To build site locally:

  quarto render
  

• How to generate reference section (based on assumptions about location of quarto-cli:

  quarto run tools/reference.ts
  

• Actions that publish website (I'm not familiar with these yet, but would be useful to document roughly when and how website is published)

[cwickham]

Include a description of the process by which previews for PRs are generated quarto-dev/quarto-web/pull/667

[cwickham]

Also include the people/orgs that have access to Netlify

[cderv]

Also include the fact that we use freeze: true which means there will be no re-rendering if a qmd source file change, unless quarto render <modified.qmd> is run locally and modified _freeze files are commited.

This applies to all .qmd using some computation. Not others.

[mcanouil]

At work, I have CI that check only the files in a PR to perform some actions on them.
Would it be worth it to add a PR command GHA, that perform quarto render (+direct commit or PR) on qmd files from a PR? /render.

[cderv]

I believe you are discussing the last point I shared - IMO this would be better in another thread discussing a change of workflow. Anyway, everything is possible yes with Github action. We could indeed do that - I have thought of that too. Though, this would mean changing the workflow, and maintain some computation environment in the CI (which we don't for quarto web at the moment). For now, we are avoiding setting and maintaining R, python or Julia env there.

After thinking about it, I found that using freeze: true workflow with local rendering was the easiest for the website and it was just a matter of adapting my workflow for quarto-web contribution.

Happy to adapt the action if we think that is worth it, but sometime less maintenance burden is also good 😄