Add isolate feature

[robdodson]

This adds a (very experimental) feature to improve the quality of life for folks who are developing or authoring content on web.dev.

npm run isolate can be used to move all files out of src/site/content and into an _exile directory which will be ignored for builds. isolate takes an optional glob (or space separated list of globs) of files that should be preserved.

npm run integrate will restore all of the files in _exile to their previous location. It will also delete the _exile directory.

Example usage:

# Move everything except the style-focus directory to _exile
npm run isolate -- src/site/content/en/accessible/style-focus/**

(Do some work on style-focus/index.md)

# Restore everything from _exile back to src/site/content
npm run integrate

Benchmark

Without isolate:

• Initial Eleventy build: 10.48 seconds
• Eleventy rebuild: 8.27 seconds

With isolate:

• Initial Eleventy build: 1.06 seconds
• Eleventy rebuild: 0.53 seconds

Changes

Changes proposed in this pull request:

• Adds isolate and integrate npm scripts
• Adds git commit hook to prevent committing while the _exile directory is active
• Prevents authors collection from throwing if there are authors without posts

[github-actions]

Alex Recommends Report

Alex recommends the following language changes, but Alex is a regular expression based algorithm, so take them with a grain of salt.

README.md

Level	Location	Word	Recommendation
⚠️	62:36	master	master may be insensitive, use primary, hub, reference instead
⚠️	63:20	just	just may be insensitive, try not to use it

[netlify]

Deploy preview for web-dev-staging ready!

Built with commit 17f6168

https://deploy-preview-3920--web-dev-staging.netlify.app

[robdodson]

Percy failure can be ignored. It's flaking on an image (related to #3804).

[devnook]

Left some comments. Also - maybe consider adding a test for it?

[nhoizey]

Wouldn't it be enough to restrict the number of items in every collection when the environment is "dev"?

[robdodson]

Wouldn't it be enough to restrict the number of items in every collection when the environment is "dev"?

Maybe, though I think that would require editing the code for all of our collections to use a common filter and we'd need to ensure we use it for new collections as well. It's not a bad idea though and may be safer than physically moving the files (though that seemed to work surprisingly well). I'd also need a way to specify to the filter that it should allow certain posts to remain in the collection(s) (basically whichever post or directory of posts I'm working on).

[nhoizey]

I agree it might not be easy, and you probably don't want to remove items from a navigation collection, for example… 😅