website: Graphile Engine 4.0 docs migrated to build.graphile.org

[jemgillam]

Description

I noticed we have yet to migrate over the Graphile Engine docs. This is needed before we refresh graphile.org.

The docs on build.graphile.org are now versioned. "Current" is 4.x and "Next" is the new version. This reflects how postgraphile.org is currently.

Almost all of the content is a straight copy from https://www.graphile.org/graphile-build/ with exceptions:

• The introduction has a bit at the top taken from https://github.com/graphile/graphile-engine/tree/v4/packages/graphile-build with some new copy explaining the name change to Graphile Build

• graphile-build-pg still has its own section, so has its own place within the codebase for versioning. The wording in the overview has been taken from https://github.com/graphile/graphile-engine/tree/v4/packages/graphile-build-pg

• I have sneaked in some tweaks to the dark mode contrast

To fix

There's two things I think would be nice to fix, but this can be reviewed and merged without:

1. There are now two dropdowns for the versioning. One for each project (graphile-build and graphile-build-pg). I think it would be nice to put in vertical dividers in the nav bar between the items, but apparently this isn't possible with docusaurus as it only allows specific items in the navbar. Perhaps it can be done with CSS borders. Another hacky option which I think is too overkill is detailed here: https://stackoverflow.com/questions/69173994/docusaurus-2-how-to-add-custom-react-component-in-navbar

2. Our old site has a neat solution to tidy up the table of contents where arguments in brackets are replaced with .... It would be nice to replicate this:

OLD

NEW

3. I've noticed postgraphile.org has nice styling for the highlighted line in a code block, I'd like to replicate that here.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 32cd214

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR