Read Build Output Before Editing Random Files

A terminal error is not punishment.

It is evidence from the build system.

Build cleanly

Run:

bundle exec jekyll build

Read the complete output once.

Identify:

• source path;
• destination path;
• environment if shown;
• regeneration/build status;
• warnings;
• errors.

Error-first discipline

When a build fails:

1. capture the first relevant error;
2. identify the named file/path/line if provided;
3. classify the stage;
4. change one thing;
5. rebuild.

Do not scroll to the last stack-trace line and edit whatever filename looks familiar.

Warning vs failure

A warning can matter without stopping the build.

Record whether the command exited successfully and whether output was generated.

Build output is not the only evidence

A successful terminal result does not prove:

• every link works;
• every image loads;
• metadata is correct;
• page content is semantically correct.

It proves a narrower claim:

Jekyll completed the build according to the current inputs/configuration.

Checkpoint

Save one successful build log excerpt and annotate what each meaningful line proves — and what it does not prove.